Ingmar’s shameless self-blagvertisement.

August 27, 2008

KDE on Exherbo

Filed under: Exherbo,KDE — ingmarv @ 5:53 pm
Tags: ,

In between all the things a developer can possibly do in Exherbo, we’ve finally found the time to package KDE for Exherbo! A bit on the late side, but better late than never. Meanwhile, while you are testing KDE 4.1.0 on Exherbo, we’ll be working on KDE 4.1.1, our first real KDE bump. ๐Ÿ™‚

For those of you who are curious, you can find the git repository at here. To clone it install dev-scm/git and run

git clone git://git.exherbo.org/kde.git kde

Those of you who use(d) Gentoo will notice that we’ve changed quite a few things, most notably: parts.
As you’ll see if you followed the gitweb link, we’re not offering split KDE packages. Instead we hope to be able to use parts when that has been fleshed out properly. In practice this means that one exheres maps to one KDE tarball, as provided by upstream. Parts will still allow you to select what KDE programs you do or do not want to install.

In general we want to stay as close to upstream as possible, and this is just another result of that. After all the time we spent on packaging KDE on Gentoo, we’re not convinced that splitting up everything, in a source distro, is the way to go. We’d better take that effort upstream instead. If we ever do split packages in Exherbo we will definitely not split it out in one package per sub-directory but instead we’ll only add packages that we know people will like to use, or disable.

I must say I was really surprised by the quality of this release, and no doubt KDE 4.1.1 will be even better, so enjoy!

(Logo by Ida Jensen, with changes by Anders ‘arkanoid’ Ossowicki, thanks!)

Advertisements

August 25, 2008

New Exherbo stages

Filed under: Exherbo — ingmarv @ 9:12 pm
Tags:

It’s about time I start blogging about Exherbo

We’ve been making a fair bit of progress recently. Even though, at this stage, we focus on improving exheres-0, the packaging format, we already have lots packaged. More on that later.
Up to now we’ve been neglecting to build newer stages, which, given how fast exheres-0 changes, makes it slightly annoying to install Exherbo on real hardware, or to quickly create a chroot to try new things out.
Hence why over the past days Bo ร˜rsted Andresen (zlin) has been working on scripting stage building.

The process is really rather simple, and goes roughly like this:

  • Create target directories:


    mkdir ~/stage
    cd ~/stage
    mkdir -p ~/stage/{etc,var/db/paludis/repositories/installed,var/db/unpackaged,var/cache/paludis/metadata,var/cache/paludis/distfiles,var/tmp/paludis/build,var/repositories}
    chown paludisbuild:paludisbuild ~/stage/var/tmp/paludis/build
    chmod g+rwx ~/stage/var/tmp/paludis/build

  • Configure paludis in ~/stage/etc/paludis, as you normally would when setting up a new system.


    mkdir ~/stage/etc/paludis/
    vi ~/stage/etc/paludis/bashrc
    ...

  • Check out Arbor from git and bind mount it in the right place.


    git clone git://git.exherbo.org/arbor.git

  • Use on the host system:


    echo "/location/to/stage" >> /etc/paludis-stage/specpath.conf

  • Install the basesystem and make sure sys-apps/skeleton-filesystem-layout gets installed first


    paludis --install --environment :stage baselayout
    paludis --install --environment :stage system
    paludis --install --environment :stage dhcpcd vim gdb strace colordiff screen

  • Chroot to the stage you just built, and rebuild everything in the chroot:


    paludis --install --dl-reinstall always everything

  • Work out what is broken and go fix it.
  • This is a temporary solution pending a new resolver which will make using Paludis’ binary packages (pbins) feasible (and thus superior). Until that resolver is released we’ll attempt to keep these stages for x86 and amd64 updated.

    You can find his updated stages here:

  • Exherbo amd64 (154M)
  • Exherbo x86 (142M)
  • And bzipped tarballs, for those of you who don’t have lzma around yet:

  • Exherbo amd64 (233M)
  • Exherbo x86 (221M)
  • Safety first kids, and check the sha1sums before using them. ๐Ÿ˜‰

    Create a free website or blog at WordPress.com.