My thoughts on Slackware, life and everything

Tag: libreoffice (Page 12 of 20)

LibreOffice 4.1.3 for Slackware 14.0 and -current

There is a new source release of LibreOffice.- thanks Willy for notifying me this morning. The new 4.1.3 is another stability and bugfix release. Note that the developers are stating that LibreOffice 4.1.3 “is suitable for early adopters and private power users โ€” for conservative requirements, we refer you to LibreOffice 4.0.6 from the previous series“. But, I think you can safely upgrade.

The fresh LibreOffice 4.1.3 packages for Slackware are available in my 14.0 package repository –ย  I just uploaded them. Remember, they will work on Slackware-current just as well. Note that I ship my LibreOffice 4.1 packages with additional “libreoffice-dict-<language>” packages, containing dictionary and spellchecker support!

If you are still running Slackware 13.37 you should stick with LibreOffice 3.6.7 for which I also have packages.

Please select one of the mirrors as your preferred download location, because they offer bigger bandwidth than the master site at slackware.com.

You can subscribe to the repository’s RSS feed if you want to be the first to know when new packages are uploaded.

Cheers, Eric

Libreoffice 4.1.2 packages and the blog is back up

harrierOh my. The server which hosts my blog, as well as sbopkg.org, rlworkman.net, the SlackBuilds.org mailing lists and several more personal web sites, and on top of that is also known as “mirrors.slackware.com“, lost both of its RAID-configured drives. One drive is completely dead but Robby Workman was able to rescue much of the data on the other drive. It’s still a mystery as to why two disk drives failed at the same second, and accusing fingers are being pointed at the on-board SATA controller of the server.

Fortunately, Robby managed to install Slackware anew, and configure it back to operational status. Only a lot of mirror data is still not available but that is being sucked back in from other Internet mirror servers, so I expect that full services will be restored pretty soon.

My blog and Wiki are fully restored but I have switched to a backup twice a day (I used to backup once a day) just to be on the safe side…

TekLinks, the company which hosts the server in its datacenter, has provided full support in order to get the server back up and running again as fast as possible, thanks for that!

 

And now, on to the topic which I could not write aboout since the blog was down (but Willy helped with that) ๐Ÿ™‚

I finally managed to re-write the libreOffice.SlackBuild for the 4.1 releases. It took a while to get everything right, and get the various language dictionaries properly split off into their own packages. Just when I had built libreoffice-4.1.1 there was a source release of 4.1.2 so I never made my 4.1.1 packages public and instead went for the newest release.

If you want to read more about the improvements of the 4.1 release, you should read the official announcement of 4.1.0. The main focus is on interoperability (with the arch rival MS Office of course). More detail is to be found in the “4.1 new features and fixes” article.

LibreOffice 4.1.2 packages for Slackware can now be obtained from my 14.0 package repository – they will work on Slackware-current just as well. Note that there are now additional “libreoffice-dict-<language>” packages!

If you are still running Slackware 13.37 you should stick with LibreOffice 3.6.7 for which I also have packages.

They are also available from several mirrors. Remember, the mirror sites usually have a bigger bandwidth available than the master site! If you are a mirror administrator, and want to be added to the list, contact me.

Here is the shortlist:

You can subscribe to the repository’s RSS feed if you want to be the first to know when new packages are uploaded.

Cheers, Eric

So I finally packaged VLC 2.1. And what about LibreOffice?

VLC

Finally, the daunting task of compiling 12 packages for VLC has come to completion. I created packages for the latest VLC 2.1 (codenamed ‘rincewind’… who the heck keeps thinking that these half-arsed nicks are useful). Like with the release candidate which I packaged last month, the internally used libraries are up to date again (ffmpeg, fluidsynth, libass, libcdio, libdc1394, libdvbpsi, libebml, libmatroska, libva, opus, orc, schroedinger, vcdimager, vo-amrwbenc, and x264).

Those of you who are running Slackware 13.37, 14.0 and -current will rejoice ๐Ÿ™‚ That being said, it is likely that this is the last major VLC update for which I will produce a Slackware 13.37 package – the effort is just becoming too big.

The 2.1 release is the culmination of nearly two years of work by the team, squashing over a thousand bugs (although it is not mentioned anywhere how many of those were caused by actually coding the 2.1 branch). More importantly, the commit history shows that VLC is very much alive, evidenced by the fact that 140 code committers do not belong to the actual VideoLAN team. Good news because my expericnce was that the 1.x and 2.0 development cycles have actually caused a decrease in the quality and robustness of VLC as an allround media player. Let’s see if 2.1 will turn this around. With a new audio core and lots of work on improving the ports to other platform, I really hope that much of the deficits of the video decoders which made me switch back to MPlayer as my video app of choice, have been addressed as well.

Where to find my new VLC packages:

Rsync acccess is offered by the mirror server: rsync://taper.alienbase.nl/mirrors/people/alien/restricted_slackbuilds/vlc/ .

My usual warning about patents: versions that can not only DEcode but also ENcode mp3 and aac audio can be found in my alternative repository where I keep the packages containing code that might violate stupid US software patents.

libreoffce_logoLibreOffice

My latest LibreOffice packages (for Slackware 14) are version 4.0.5. In the meantime, those hard-working LibreOffice developers are almost at version 4.2.1… so what happened to the ‘alien’ builds of LibreOffice 4.1?

Well, during the packaging of 4.0 I noticed that the dictionaries which are now being offered as a source tarball, including many languages, needed another way of building and installing. I have been trying to find time to investigate and come up with proper packages, but I ran into a snag with the SlackBuild script and kept telling to myself that I would look into it right after the next KDE… OpenJDK… Calibre… whatever package would have been created. To be honest…. I am swamped with work during my paid daytime job and I spend more hours per week at work. It takes time to finish the bigger projects (like LibreOffice) in my spare time. Be patient, packages will be released eventually.

Oh yeah…

I helped my son today with the home-made pizza he had promised to create. I did something I realized I had never done before… I created the pizza dough from scratch: flour, yeast, water, olive oil, salt. Kneading the dough, seeing it rise and flattening it out to an oven-plate sized pizza bottom was very rewarding. Eating the pizza was rewarding as well! I have promised myself to finally bake that Focaccia bread which I have been wanting to try forever.

And finally:

Anyone with a Google Nexus tablet out there and experience with unlocking it, putting some brand of real Linux on it? I am going to pick up my own ARM port after Slackware 14.1 is released and besides my personal targets (getting it to boot on my TrimSlice and my ChromeBook) I was wondering how open the Google Nexus tablets really are with regard to having linux device drivers available. I am dead-curious about seeing how well Slackware behaves on a touch device… and both the Nexus 7 and Nexus 10 look like they are awesome devices.

Be good! Eric

 

 

LibreOffice 3.6.7 (last in series) packaged for Slackware 13.37

I thought that with 3.6.6 the LibreOffice developers had released the last update in the 3.6 series. However, there is yet another release. and it looks like 3.6.7 is really going to be the final incremental release. LibreOffice 3.6.7 is a bugfix release (changes in 3.6.7.1 and 3.6.7.2) which was added to the release schedule in a late stage. This means end-of-life for the 3.6 series and everybody is encouraged to migrate to the stable 4.0 series.

These LibreOffice 3.6.7 packages which I am making available have been built on Slackware 13.37. They can be installed on Slackware 14 as well, but of course I have LibreOffice 4.0.4 packages (32bit, 64bit) in my repository for Slackware 14 and -current. Perhaps it is time for you to upgrade your Slackware along with LibreOffice in a little while, if you are still running 13.37? The new Slackware 14.1 should not be too far off.

The LibreOffice 3.6.7 packages are available here:

Eric

Last week’s harvest

I was a bit too busy and tired to write something on my blog during the past week, but now that it is weekend again, there is room for some updates.

Flash Player Plugin

There was yet another security update for Adobe’s Flashplayer Plugin. I updated my package to the latest version. Note that if you are using my Steam Client package, you will probably have installed the flashplayer-plugin in order to see all the news in the Steam Store. If you are on a 64-bit Slackware platform with multilib, you should not just update the 64-bit flashplayer-plugin but also convert the 32-bit package into a “compat32” version and upgrade the 32-bit package you will already have installed for Steam:

# convertpkg-compat32 -i flashplayer-plugin-11.2.202.285-i386-1alien.txz
# upgradepkg --install-new /tmp/flashplayer-plugin-compat32-11.2.202.285-x86_64-1aliencompat32.txz

KDE

The kdelibs package in my ktown repository (KDE 4.10.3) has been patched to prevent application crashes. Coincidentally this patch has also been applied to the kdelibs package in slackware-current.

Slackware Dependencies

A nice and fast tool to discover and query dependencies between Slackware packages is sbbdep which stands for “Slack Build Binary Dependencies”. Its author, a4z, released version 0.2.0 last week. I use this tool to assist me when determining the build order of packages for my ARM port.

ARM Port

Speaking of which, there is an interesting thread going on on LinuxQuestions, regarding ARMedslack and the Raspberry Pi. Someone who goes by the nick “Ahau” and comments on my blog from time to time, is working on a hard-float port to the armv6 hardware platform – the heart of the Raspberry Pi. He is using my ARM source tree for this, has given me good feedback which resulted in bug fixes, and his ultimate goal is to create a new ARM version of Porteus. The most recent part of the LQ discussion centered around my decision to split the libtinfo library (terminfo) out of the libncurses(w) library. This is the ncurses developers’ intention for the future, however it causes issues when compiling software which is not querying the system properly and assuming that only libncurses(w) is required for linking.

I had nearly decided to revert my decision and integrate libtinfo again into libncurses(w) when ponce pointed out a patch which I had already seen in Fedora’s ncurses package source. Perhaps I will apply that patch to my ncurses package because it seems to resolve all the linking issues we have been running into lately.

LibreOffice ARM?

And more good news – it took two days of compiling because I forgot to enable distcc, but I managed to create LibreOffice packages for my ARM port, using the SlackBuild script with which I already compiled LibreOffice 4.0.3 for x86 and x86_64 platforms last week (I needed one additional patch to work around the newer boost-1.53 which I have in my ARM tree). I have not had the chance to install the packages and run the LO Writer to see if I created working binaries… but the build log did not show errors which is promising!

Desktop Environments other than KDE or XFCE

Long ago, I created a package for razor-qt which is a minimal (lightweight may be the better word) desktop environment based on Qt. In other words, it looks beautiful (by not using GTK) and does not have the sluggishness people complain about when they run that other Qt based desktop environment (KDE). I was thinking about what I would have to add to a filesystem image for the ARM ChromeBook which I should finally get ready and distribute… I do have KDE packages, but KDE felt like just a bit overweight for the ChromeBook. I do not really like XFCE (don’t get me wrong, technically and functionally it’s not bad at all, but GTK does not have any visual appeal to me) and therefore I felt compelled to re-visit razor-qt.

Razor-qt does not come with its own window manager, instead it allows you to pick one of the available window managers it finds on your computer when it starts for the first time. Razor-qt will work well with KDE’s window manager KWin, but it works best with OpenBox. And since that is not part of Slackware, I added an openbox package as well to my repository (which was the moment that I found out I had never released my original razor-qt package… no idea how I could have forgotten that).

I decided that I am going to build armv7hl packages for razor-qt and openbox so that the ChromeBook has a nice and fast, good-looking desktop environment next to XFCE. They will be uploaded to my separate “alien” subdirectory of the ARM package tree, where I will upload the LibreOffice packages as well.

KDE Display Manager

The KDE Desktop Environment is transitioning to Plasma Workspaces 2. Two changes are worth mentioning because they will have a big impact: Many “user-interface centric” applications will be re-written in QML (Qt Modeling Language). More importantly, the X.Org display server of old will be abandoned for the Wayland protocol server. Wayland gives you a 3D-enabled display server from the start, instead of the current practice of running a 3D compositor (KWin, compiz) as an extension under the 2D X.Org display server. Future support of Wayland requires a rewrite of KWin (KDE’s window manager) but also forced a decision to say goodbye to the KDE Display Manager (KDM) which is the graphical login program which greets you when you boot Slackware in Runlevel 4. A blog post by Aaron Seigo gives a lot of insight in the process that preceeded this decision.

It looks like SDDM (Simple Desktop Display Manager) is a contender for replacing KDM in a future release of KDE. Initially, SDDM had a hard dependency on PAM, but thankfully the developer is friendly towards Slackware. After a short discussion on Google+ he created a preliminary “pam-less” version which I tested. Those tests went OK and the changes were added to the main source. So it is with pleasure that I announce the package which I added to my repository. You can already try it out, if you just add a couple of lines to Slackware’s “/etc/rc.d/rc.4” script. Directly below the line that says:

echo "Starting up X11 session manager..."

you add:

# ----8<----------------------------------------------------------------
# Use Simple Display Desktop Manager
 if [ -x /usr/bin/sddm ]; then
 exec /usr/bin/sddm
 fi
# ----8<----------------------------------------------------------------

Enjoy!

Eric

« Older posts Newer posts »

© 2024 Alien Pastures

Theme by Anders NorenUp ↑