On Tue, Nov 08, 2005 at 12:53:47PM -0600, Manoj Srivastava wrote: > On Wed, 9 Nov 2005 00:22:23 +0900, Horms <[EMAIL PROTECTED]> said: > > > On Tue, Nov 08, 2005 at 09:01:24AM -0600, Manoj Srivastava wrote: > >> On Tue, 8 Nov 2005 14:26:17 +0100, Sven Luther > >> <[EMAIL PROTECTED]> said: > >> > >> > On Tue, Nov 08, 2005 at 08:30:53PM +0900, Horms wrote: > >> >> On Tue, Nov 08, 2005 at 11:36:13AM +0100, Sven Luther wrote: > >> >> > On Tue, Nov 08, 2005 at 11:19:36AM +0100, Jonas Smedegaard wrote: > >> >> > > -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > >> >> > > > >> >> > > On Tue, 8 Nov 2005 11:31:10 +0900 > >> >> > > Horms <[EMAIL PROTECTED]> wrote: > >> >> > > > >> >> > > > Waldi, can you coment on how to add a recommends to images > >> >> > > > on a per-flavour basis? > >> >> > > > >> >> > > Isn't per-flavour control hints one of the new features of > >> >> > > the soon-to-be-in-sid kernel-package? > >> >> > > > >> >> > > If so, I suggest using that instead of bloating linux-2.6 > >> >> > > packaging unnecessarily. > >> >> > > >> >> > linux-2.6 packaging already has quite nice per-flavour > >> >> > dependency handling, thank you. > >> > >> Would it not be nice to push it down into the underlying tool, so > >> that even endusers get a nicely hinted per flavour images, as > >> appropriate? I mean, we cater to all users, not just those that use > >> official Debian kernels. > > > Don't we need to handle the control file ourselves because we make > > multiple make-kpkg invocations which all come together to form a > > single source package? > > I am planning on constructing the control file from bits even > in the default install so that the uml and xen images do not show up > in the control file but are never built, and we get all the "package > exists in control file but not in changes" warnings. Perhaps there > can be a set of mini-control files concatenated together into a > control file before it is read by Make?
Manoj, we already do this, see the templates dir and bin/gencontrol.py. I told you that earlier already. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
