<some cookers might want to try this at home too... if you've got some
weird hardware (alpha, ppc, sparc or something else), join the fun!!>
> > Now, what you could do is the following (if you have a spare machine and
> > way too much time on your hands):
> > - Install the 7.1 release of mandrake's sparc distro;
> I've done that. Been using it on my Ultra1 Creator since it came out. It's my
> daily workhorse because the 20" Trinitron screen is just so nice to look at and
> the keyboard is nicer than the PC one I have. I also run LM on my Athlon
> 550MHz and I'm looking forward to the upcoming 7.2 realease with KDE 2 on it.
2 machines, one sparc, one x86. even better! I've got an alpha and a
celeron, both compile cooker once a week. I also do it on the celeron to
collect the buildoutputs, it's always nice to have them --> gives you
something to compare the non-x86 buildoutputs to. I keep the systems
up-to-date with autorpm (available in contrib). On my x86 box I only
install the rpm's which are made by mandrake. On my alpha box I install
the rpm's it makes itself.
/mirrors/cooker cooker distro (x86). I use this to give my x86 quick
autorpm access to the rpm's
/mirrors/contrib/SRPMS contrib SRPMS
/mirrors/SRPMS cooker SRPMS
(these directories are mirrored from sunsite.uio.no, a crontab with
fmirror syncronizes them every hour).
/misc/linux/mandrake/bin/ place where I keep some scripts
/misc/linux/mandrake/buildout/cooker/alpha/ place where I store the
buildoutputs http://d10179.dtk.chello.nl/build/cooker/alpha/
BM/ packages that need to be BM-ed
OK/ * packages which are "OK"
arch_excl/ * packages that are arch-excluded
broken/ src.rpm itself is broken
dependancies/ package is missing a dependacy to build
fixed_uploaded/ packages I've fixed & uploaded to mandrake
interactive/ packages that require human intervention to
build
kde/ packages that require kde (kde is currently
broken on my alpha
box)
perl5/ packages that have the perl .bs & .packlist
problem
perl5_man/ packages that have the perl5/man problem
problem/ * packages that have other problems
root_only/ packages that require root to build.
* these get sorted by the script
/misc/linux/mandrake/cooker/ place where I store the *.alpha.rpm and
*.noarch.rpm files
/misc/linux/mandrake/results/ place where I store a quick comparison
between the alpha and x86, (which packages aren't building, is it a
common problem, or a alpha related one, etc.)
(/mirrors and /misc are automounted --> available on both boxen).
I've made 3 useraccounts (contrib, cooker & crypto) on each box, with
local homedirectories. I logon to the console in each of those accounts
and run:
while true
do
/misc/linux/mandrake/bin/build_cooker.sh
sleep 900
done
and this will continue building...
Attached you'll find:
build.tar.bz2
/etc/autorpm.d/ on my alpha
/misc/linux/mandrake/bin/
/root/fmirror_conf/
autorpm_x86.tar.bz2
/etc/autorpm.d/ on my x86
> > - mirror the current cooker (or 7.2b) SRPMS;
> > - start systematically rebuilding and updating your system to the
> > current cooker (or 7.2b) distro (I'll help you out with a few scripts
> > that can make life easier);
> > - report bugs to the cooker list.
> > Of course only a mad man would do something like that ;-)
> If this had come about two weeks ago, I may have had the time. Unfortunately, I
> leave for Europe in a week and have quite a few things to tie up before then.
> If I started on it then I'd have to leave it half-cooked ; )
Just set it up and let it run for a while... see how far it gets... and
maybe make the buildoutputs browseable for others (we might be able to
help).
> Could you give me some more info on how long it would take and sort of a quick
> outline on the process?
Setting it up? With the stuff attached here it should be quite quick.
The scripts have proven themselves.. Building the distro could take some
time, depending on your machine. My 433MHz alpha takes 2-3 days to do
it.
> I'd really like to work on it but I won't be back from Europe until about a week
>into
> October. I might have a chance to get something started though. It depends on what's
> involved and who else is doing what, if anything.
The hardest part is doing all the manual upgrades. autorpm tries to
update package by package, which doesn't work all the time. Also you'll
find that sometimes stuff breaks. For instance, the kernel on x86 is
having VM problems, and XF86 on my alpha crashes the box, qt2 doesn't
work on alpha (and thus kde2). These are things we need to live with,
it's a joy running a development distro... ;-)
> I should be in Paris late in September and I thought I might try to
> stop off at the LM offices there. Is this the address of their office, or is
> it just a mailing address?
> MandrakeSoft S.A. : 43, rue d'Aboukir - 75002 Paris - France
If you're in the Netherlands, or in Eindhoven specificly, please drop
by. ;-)
> I have never been to France before, so I don't have a clue about how to get
> around in Paris. Is there even an office to visit, or is it just a lot of
> people working remotely?
I don't work for mandrake (yet?). I've been to the Paris Office once &
met the mandrake hackers. Very friendly people.
Stefan
autorpm_x86.tar.bz2
build.tar.bz2
