Re: Bug#278729: kernel-image-2.6-k7: kernel-image-2.6*-k7* and 2.6*-686* should
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. Additionally, I would have thought that pushing code down to underlying tools and reducing the maintenance burden would be a good thing. Either way, is it possible to add recommends on a per-flavour basis, and if so, how? Not sure, i know we can add dependencies though, so the same mechanism can probably quite easily be used for recomends. The Control file is a template that comes stuff that can be substituted out -- like this Suggests: =L fdutils, =ST-doc-=V=SA | =ST-source-=V On install, the -L and =ST etc are filled in with the relevant values. The idea would be to add a Recommends: =RE filed to the control file, and then the per flavour snippets can set $(recommends) variable, and the targets/image.mk substitute in the value. manoj -- Acting is an art which consists of keeping the audience from coughing. Manoj Srivastava [EMAIL PROTECTED]http://www.golden-gryphon.com/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#278729: kernel-image-2.6-k7: kernel-image-2.6*-k7* and 2.6*-686* should
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. Well, maybe, but we first need to see what happens with the intensive k-p changes you want, and i wasunder the impression that Horms wanted to use the feature ASAP. Anyway, it is implemented now, was a 5 line trivial change in gencontrol.py. Maybe you want to look at it and see if you can reuse some ? Additionally, I would have thought that pushing code down to underlying tools and reducing the maintenance burden would be a good thing. Pushing things into k-p reduces the maintenance burden only for you, but worsen it for the rest of us :). Either way, is it possible to add recommends on a per-flavour basis, and if so, how? Not sure, i know we can add dependencies though, so the same mechanism can probably quite easily be used for recomends. The Control file is a template that comes stuff that can be substituted out -- like this Suggests: =L fdutils, =ST-doc-=V=SA | =ST-source-=V On install, the -L and =ST etc are filled in with the relevant values. The idea would be to add a Recommends: =RE filed to the control file, and then the per flavour snippets can set $(recommends) variable, and the targets/image.mk substitute in the value. Yeah, and more often than not, those templates where strangely filled or not filled, probably due to miscomprehension of their mechanism. But you are missing the point, the above recomend go into the linux-2.6 debian/control file, which is uploaded as source, and it is against policy i hear to modify it at build time, so i doubt that the approach you use is compatible with our needs. Please have a look at debian/templates, debian/bin/gencontrol.py and the debian/control target in debian/rules. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#278729: kernel-image-2.6-k7: kernel-image-2.6*-k7* and 2.6*-686* should
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? -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#278729: kernel-image-2.6-k7: kernel-image-2.6*-k7* and 2.6*-686* should
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 -- Absurdity, n.: A statement or belief manifestly inconsistent with one's own opinion. Ambrose Bierce, The Devil's Dictionary Manoj Srivastava [EMAIL PROTECTED]http://www.golden-gryphon.com/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#278729: kernel-image-2.6-k7: kernel-image-2.6*-k7* and 2.6*-686* should
Sven Luther [EMAIL PROTECTED] wrote: 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: 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? I'm still not entirely sure that I understand how this would fit into what linux-2.6 is doing. Perhaps if I breifly explain what it does you can fill in the gaps. First up there are templates in templates/ and defitions the architectures, sub-architectures and flavours there are in arch/. These definitions are growing to include information about dependancies, kernel header directories and stuff like that. arch/ also includes configure fragments. Before dpkg-buildpackage is run, a script is run which produces a control file that contains all the packages for all architectures, this is built using the information in templates/ and arch/. Simiarly, rules.gen, which rules drives to produce the packages on each architecture is produced. Its combination of rules.gen and control which allows architectures, sub architectures and flavours to be added and removed in a flexible manner, just by manipulating arch/ At run time, some additional mangling occurs to produce the .config files based on the fragments in arch/ In a nuthsell kernel trees are unpacked, the appropriate .config is produced and placed in the tree and make-kpkg is called. I should note, that I didn't actually write the system, and I'm still learning how to drive it. Waldi and Dilinger know a lot more about it, perhaps they can fill in some of my gaps. Manoj, we already do this, see the templates dir and bin/gencontrol.py. I told you that earlier already. Is there really any need to be so aggressive? Yes there is logic in there, and yes its coming along quite nicely. But to be honest, the more logic we can push back to kernel-package, the less we have to worry about. And I'm all about worrying less. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#278729: kernel-image-2.6-k7: kernel-image-2.6*-k7* and 2.6*-686* should
On Wed, Nov 09, 2005 at 12:44:53AM +, Horms wrote: Manoj, we already do this, see the templates dir and bin/gencontrol.py. I told you that earlier already. Is there really any need to be so aggressive? Well, notice this is the second time i asked him to look at how we do, and it was mostly ignored. I am a bit warry of this approach, which basically consists of reimplementing everything, without caring about the work done in the past months he was not involved in. In france we have a saying about throwing away the baby with the baby water, not sure if it translates well though. Yes there is logic in there, and yes its coming along quite nicely. But to be honest, the more logic we can push back to kernel-package, the less we have to worry about. And I'm all about worrying less. Indeed, but it would be good for Manoj to have a look at what we do before doing intrusive changes all alone, and breaking our stuff, as did happen with the 10.008 upload to unstable. We where all doing test build last nights, and i believe that the 10.008 upload to unstable was premature, so let's only hope this gets fixed quickly, as we are not able to make new kernel uploads until this is fixed. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#278729: kernel-image-2.6-k7: kernel-image-2.6*-k7* and 2.6*-686* should
Processing commands for [EMAIL PROTECTED]: reassign 278729 linux-2.6 Bug#278729: kernel-image-2.6-k7: kernel-image-2.6*-k7* and 2.6*-686* should recommend libc6-i686 Bug reassigned from package `kernel-image-2.6-k7' to `linux-2.6'. retitle 278729 some i386 images should recommend libc6-i686 Bug#278729: kernel-image-2.6-k7: kernel-image-2.6*-k7* and 2.6*-686* should recommend libc6-i686 Changed Bug title. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
