Lucas Nussbaum wrote:
On 01/10/08 at 17:11 +0100, Roger Leigh wrote:
Could you possibly explain what exactly you would like to do with this
feature? I would be happy to add some general mechanism to sbuild,
such as your patch, but I'd just like to understand the use case for it.
Hi,
Since that feature could help me as well, I'm jumping in and describing
my use case.
I often run rebuilds with two different "configurations", to be able to
compare the results. For example:
- stock Debian unstable
- Debian unstable with newer GCC
The "newer GCC" part is implemented by adding a line in
/etc/apt/sources.list and running apt-get update && upgrade, so apt will:
- install the newer GCC
- if needed, install the newer deps not part of build-essential (think
of GCJ).
I implemented that by using two chroots: unstable and unstable-gcc. But
it's painful to maintain both chroots, and it would be much more easier
to customize my stock Debian unstable chroot before building, using a
hook script.
How would you prefer to choose which variant to use? Would you just
add/remove/alter the hook script, or would you like sbuild to be able to
pass something in the environment to customise the script so that you
can invoke sbuild with e.g. a new option which can set the desired
behaviour in your script.
Regards,
Roger
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
