On Mon, Feb 14, 2005 at 08:26:03AM +0100, Francesco Paolo Lovergine wrote:
> On Mon, Feb 14, 2005 at 12:04:12AM +0100, Michael Banck wrote:
> > On Sat, Jan 29, 2005 at 02:00:57AM +0100, Santiago Vila wrote:
> > > This package should use /usr/share/sbuild instead of /usr/lib/sbuild,
> > > as it does only contain architecture-independent stuff.
> >
> > Actually, I think we should move the stuff from /usr/lib/sbuild to
> > /usr/bin, possibly having some prefix to avoid namespace pollution. Does
> > anybody what was the rationale for having it in /usr/lib in the first
> > place?
> >
> > How about /usr/bin/sbuild-apt instead of chrapt, etc.?
> >
>
> It is surely more correct, but for the problem of eventually breaking other
> user's scripts. Indeed, wanna-build sbuild scripts can be considered a
> different fork, so there is no reason to retain compatibility on that regard.
Moving the scripts out of /usr/lib/sbuild would break any 3rd party
stuff anyway I guess, as those are not in the default search patch and
likely to be called with an absolute path.
Should we proceed here? Maybe we should classify the scripts in being
useful for sbuild or for chroot handling in general.
updatechroot, checkchroot, upgradechroot, chr-hold, chrapt, gochroot and
chr-unhold look like chroot-mangling scripts.
They could be renamed to chroot-{apt,hold,update,upgrade,unhold,go}.
abort-current-build, add_sbuild_user are sbuild oriented, their names
are unlikely to clash with any other package and could stay.
dobuildlog does not look to be generally useful, but we could ship it in
examples or so?
common_functions is pretty Debian-centric the scripts should perhaps be
changed to just look in ~/build/chroot-$dist like sbuild does now as
well and drop common_functions.
the rest is not executable, and could go into /usr/share/sbuild.
What do you think?
Michael
--
Michael Banck
Debian Developer
[EMAIL PROTECTED]
http://www.advogato.org/person/mbanck/diary.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
