Re: Description of tasks
Martin Michlmayr <tbm@cyrius.com> writes:
> * Ingo Juergensmann <ij@2004.bluespice.org> [2004-07-14 12:04]:
>> Let me use an old example (just as an example, not as a base for a new
>> discussion):
>> Administrating a buildd is surely somewhat that sounds complex and difficult
>> to many people. Setting up a buildd and all the stuff is not something that
>> average Joe User can do.
>> But that doesn't mean that other people can't learn how to do this.
>> When I started with my m68k buildd, even some porters didn't really know how
>> to setup a buildd. We had to ask Roman Hodek for details. But we (i.e. m68k
>> porters) have learned and shared that knowledge, which led to a broad number
>> of m68k buildd admins, giving a redundancy not only in buildd machines but
>> as well in buildd admins.
>
> I've never tried to set up a buildd (only sbuild) but I've heard
> before that it's fairly complex and hardly documented. Since you have
> obtained the knowledge and insights about setting up a buildd, have
> you documented this to make the knowledge available to everyone? Or
> is this a shared secret only passed along within the m68k cabal?
Currenlty I'm not aware of it being documented. But it was easy to get
one of the m68k buildd admins to walk me through it when I wanted to
set up the buildd.
And the knowledge is being used to develope multibuild including docs
and packaging for it. Most of the ugly things setting up a buildd will
be done in the maintainer scripts instead of by hand.
In the future [yes, I know this is all still vapourware till we upload
something] you just run "apt-get install buildd" and read
/usr/share/doc/buildd/*.
Unless you are complety new to it, pointing it to the right directory,
mirror and multibuild server to use in the debconf dialogs is all you
need to do. The intended users include people that just want to build
their local sources and mini repository the same way debian
does. Setting it up has to be much simpler and more robust than
buildd+sbuild.
> --
> Martin Michlmayr
> tbm@cyrius.com
MfG
Goswin
Reply to: