Re: RFC: autobuilder pseudo-package

2007-09-26 Thread Goswin von Brederlow
Holger Levsen [EMAIL PROTECTED] writes:

 Hi,

 On Tuesday 25 September 2007 12:25, Simon Richter wrote:
 inspired by the how to detect if inside a buildd chroot thread: would
 it make sense to have an (empty) package autobuilder that all packages
 that are not supposed to be installed on autobuilders (daemons, packages
 requiring interactive configuration, ...) can conflict against?

 Interactive configuration must be done via debconf by now.

 And not wanting to start daemon can have other reasons than autobuilders, eg. 
 eg. chroots, fai's nfsroot, piuparts... so autobuilder is not a good name.


 regards,
   Holger

I also would not make it empty but have it come with a policy-rc.d
script that returns 101. That way it nicely disables all daemons for
you. Also you could have some debconf configuration to set the
hostname and prompts to reflect it is a chroot.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



RFC: autobuilder pseudo-package

2007-09-25 Thread Simon Richter

Hi,

inspired by the how to detect if inside a buildd chroot thread: would 
it make sense to have an (empty) package autobuilder that all packages 
that are not supposed to be installed on autobuilders (daemons, packages 
requiring interactive configuration, ...) can conflict against?


   Simon


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFC: autobuilder pseudo-package

2007-09-25 Thread Goswin von Brederlow
Simon Richter [EMAIL PROTECTED] writes:

 Hi,

 inspired by the how to detect if inside a buildd chroot thread:
 would it make sense to have an (empty) package autobuilder that all
 packages that are not supposed to be installed on autobuilders
 (daemons, packages requiring interactive configuration, ...) can
 conflict against?

Simon

Just in case some depends pulls it in unintentionally?

In that case I think sbuild would just happily remove it and that
would be that. Or do you want to make it essential? :)

At a minimum you need sbuild to know about it. But I haven't yet seen
why rc policy settings should not do the trick.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFC: autobuilder pseudo-package

2007-09-25 Thread Holger Levsen
Hi,

On Tuesday 25 September 2007 12:25, Simon Richter wrote:
 inspired by the how to detect if inside a buildd chroot thread: would
 it make sense to have an (empty) package autobuilder that all packages
 that are not supposed to be installed on autobuilders (daemons, packages
 requiring interactive configuration, ...) can conflict against?

Interactive configuration must be done via debconf by now.

And not wanting to start daemon can have other reasons than autobuilders, eg. 
eg. chroots, fai's nfsroot, piuparts... so autobuilder is not a good name.


regards,
Holger


pgp0P43WRXgeY.pgp
Description: PGP signature