Yo :)

The good news:

Beside the separate cache dir, this whole multiarch thing is
now completely automated in the latest create-buildenv.sh in
svn. You can even install a Arch chroot on other distros now,
so far i have done some testing on Debian Lenny x86_64 building
for both archs and it works fine :) Other distros may work fine
too, but besides Debian there is no support for them in the script
so far.

To use it on Arch, you just have to add one more parameter for the
architecture. Thats it!

To use it on other distros, you need a pacman installation at first,
preferably pacman.static (the script will prefer pacman.static if found).
After having some breakage with alien i just unpacked the following
arch packages into the root of the debian install:
pacman, pacman-mirrorlist, pacman-static
Its a bit unclean,  but pacman is quite simple software, so i can
delete it manually if needed.
Just remember to get the correct architecture for your host system,
and you DONT need to configure pacman anymore to include the repos,
its all done by the script now, we just need the binaries :)

Apart from these changes, nothing much else has changed. Some problems
got solved the ugly way, like setting the right arch in makepkg for i686
on a x86_64 host, but so far it seems to work ;)

Also the actual buildscripts need some changes, i have done them in testing,
its just 2 lines per script or so.

The bad news:

After the next "svn up", your build env will probably be broken very badly,
you will need a deletion of the "KDEmod" dir and a complete reinstall.
Or better: do it now :) But mind that only the build scripts in testing
are done so far.

And some tips etc:

- building x86_64 packages on a i686 system is not possible
  (unless you run a customized x86_64 kernel on your i686 system)
- there are still bugs, i can smell them :)
- on Debian, pacman is very slow somehow, learn to deal with it
- stop-all.sh seems to be broken (again, after i thought i fixed it)
- you need to install repo-clean manually sometimes (better check it)

And at least, the actual "work" to get a shared build server is now
completed, we just need a big, powerful machine :) I have created a
build user on the main server, but it isnt that fast because the
machine already has a lot of stuff to do. However, if we cant find
a faster one we can use this one for now, probably with some
cpu-limiting tricks for the buildenvs. If someone wants to play with
the env on the server, just leave me a note.

Thats if for now, good night :)

Jan

Am Mittwoch 23 Dezember 2009 23:24:20 schrieb Dario Freddi: