with the new perl 5.26.1 in current you might have the bad surprise of your perl module build script breaking: this happens because upstream decided to remove . from @INC, so every perl module that uses a local directory in its own sources to have additional stuff available during building, and counts on including it because before perl-26.x this was the normal behaviour, breaks with this change, and modules like these are an awful lot 🙁
As much work has been done on LXQt, <a href=http://blog.lxde.org/?p=1100>PCMan has just proposed an alpha releasesoon. I have updated the build scripts for Slackware in my git, and this is the sbopkg queue (using my git repository with it) that you can run to install all of its components Beware that everyhting is still a rough and some things needs to be adjusted, but if you choose to install this now is also to help testing it (and report problems upstream) 🙂
Maybe someone of you had heard about the fact that LXDE developers didn’t want to get dragged into the GTK+3 mess and that they decided in march of this year to merge efforts with the Razor-qt people to develop together a lightweight DE based on Qt (see the various post on the LXDE blogand on their <a href=http://sourceforge.net/mailarchive/forum.php?forum_name=lxde-list>mailing listfor more informations on this). So they picked some stuff from Razor and PCMan wrote much other from scratch: as <a href=http://blog.
I tried to find a little time to build fresh sets of packages to have an LXDE desktop on the just released version of Slackware: you can find them in the usual place 🙂 64bit32bitas a lot of people seems to use slackpkg+, the folders linked above contain repositories compatible with Zerouno’s slackpkg extension 😉 hope that I’ll find some time to install a fresh slackwarearm-14.1 on one of my raspberries and prepare them also for that platform.
As we are developing a php database interface for a project here at work and some related functions are being deprecated starting with php 5.5.xI considered upgrading our php installs on our servers and test if it works fine with our stuff. As I’m using Slackware on my servers I managed to update the existing build scripts to build from a php 5.5.x tarball and I installed the new package on slackware64-14.
I’m fiddling with the staging branch of LXC (stuff that will go in 0.9, now at alpha state) and there are some news to report. They are migrating to python3 scripts and a corresponding API and some stuff in LUA too to substitute many of the lxc helpers (I’m using python3 and lua from slackbuilds.org). People is already doing interesting stuff with the API. Plus, lxc-attach, used to execute commands in the containers (for example, I use it for an rc.
As the new slackware is out, I wanted to try a clean install on my rasperry-pis. I referred to the super-detailed guide from dave(thanks!), but his build scriptsneeded just a little refreshing as upstream moved to a new firmware (boot changed slightly) and kernel version (ditching 3.1.9): more, they are committing on two kernel branches, one based on 3.2.27 (the default) and another based on 3.6.1. So, at first I forked dave’s build script to build a 3.
It has been some time since last post and many things happened: one of those is that I have been invited to work with the people at slackbuilds.organd I gladly accepted 🙂 Work there is really interesting and I feel like I’m learning a lot. But the thing I felt most urgent, as I had chosen Slackware to host the services I administer at work and a new version of slackware is out, is to upgrade the lxc host and containers to slackware-14.
I’m using some lxc containers to offer services with less resources than full virtualization (like kvm, virtualbox, etc.) demands for. At first I was creating the containers I needed basically following Chris Willing’s guide but, being jealous 😛 of the existing templates for the debian based distributions that allow creation of containers with a single command, I tried to assemble one for slackware 13.37, that I personally use at work and at home as a virtualization platform.
You have a full slackware installed and you want to use it as a LAMP server? here is a basic setup with phpmyadmin, if you like pretty interfaces for database administration (optional), in some easy steps (as root). This is a superquick guide, for more informations consider reading mRgOBLIN excellent article. let’s start 🙂 – make executable the init scripts of httpd (apache) and mysql – initialize the database and create standard mysql tables (I suggest to read output on screen, it’s interesting)
as I promised, I have added the necessary branches to my slackbuilds.org’s git master fork, so it will be easy to build a complete LXDE desktop using sbopkg. I used existing slackbuilds.org components, I added alien bob’s scripts adapting them to slackbuilds.org template and I wrote some from scratch. UPDATE: all the components are submitted to slackbuilds.org now so there’s no particular need to set up my repository, unless you want latest testing (but working) stuff for current.
hi, finally found the time to work a little on LXDE: I’ve prepared a second round of slackbuilds and packages based mainly on the git version of the various components (many improvements in there). hope I haven’t missed anything of the things spotted (still have to do experiments with suspend). maybe is better if I just cut and paste from the README.txt of the download folderI’m only a little disappointed for having to upgrade glib2 but, you know, it’s testing stuff 🙂
As Robby Workman has announced on the slackbuilds.org users mailing list, they started a git repository for managing their slackbuilds. 🙂 This, besides being great news, has some implications: my SBo-git repository for -current has no sense to be continued anymore, as the logic (and Robby too :D) tells me to rebase my work on their repository. It’s was also much cleaner and ordered, but I forked it on github and I started playing on it to have a branch to use to build my sbopkg queue.
as announced on slackware main site the 13.1 release of the oldest linux distribution is ready 🙂 slackware confirm itself one of the most innovative distribution in the field, with software updates surpassing latest ubuntu 😀 The SBo-git repository is ready too to be used with sbopkg on this new slackware version. if you need fresh additional packages beside slackware standard full install, I built some (using sbopkg and SBo-git) for my personal use (the list) that I gladly share:
updated SBo-git with some small fixes after the slackbuilds.org updates of 2 days ago: this is the repo at today. there’s also a new contributor, Greg Tourte! 🙂 soon I’ll fix the individual branches to do a rebase and a merge in a new branch derived from master: after all, it looks cleaner to me than apply lot of fixes to current. 🙂 I also rebuilt my x86_64 packages (soon the i686 ones will follow).
good news for who’s using sbopkg with sbo-git as a repository. tnx to 55020 for the setup instructions: I’m improving my git-fu and now, using binary patching, I will update directly the -current branch without recreating. that means, basically, that you can sync it from inside sbopkg with no need to delete/reset old checked out git files. 🙂 this will work for you if you have checked last time my 20100425 commit, if not you have to
– updated to latest slackbuilds.org status. – removed some stuff fixed/updated on slackbuilds.org. – modified gtkmm version and added custom versions of cairomm, glibmm, libsigc++ and pangomm as kindly hinted by Robby Workman ( 😀 ). if you are using my git repository with sbopkg the easiest thing to do to sync is to remove the previously cloned folder: so, if you have previously added a file /etc/sbopkg/repos.d/30-SBo-git.repo with (for example) this content
I’m done building x86_64 packages for my currents, now I’m trying the updated SBo-git (you can see all the patches at this link 😉 ) with sbopkg on a 32bit virtual machine. SBo-git it’s based on my sbopkg queue. I built the above packages with sbopkg on a freshly installed current (virtual machine), patching them by hand when sbopkg stopped for any reason: on current we have a new bash, new gcc/glibc, new kernel (and a new libpng) so many slackbuild/sources needed patches to build.
I’m working on the SBo-git repository to have a working snapshot of slackbuilds.org repository compatible with latest slackware current for the package I use. Lots of thing are changed: we have a new bash that wants stricter slackbuilds so many slackbuilds.org scripts of the 13.0 repository break on current. 🙁 but I’m fixing errors as they show while following my sbopkg queue and things go on (for the moment 🙂 ).