On Wed, Jun 27, 2007 at 11:53:17AM -0700, Steve Langasek wrote:
> Neither ensures that linux-image-2.6-686 and foo-module-2.6-686 are upgraded
> together, which is what is being asked for. This is a desirable goal,
> because without this constraint, users who have both packages installed may
> have linux-image-2.6-686 upgraded before the new version of
> foo-module-2.6-686 is available, rendering their system unusable on reboot.
Got it.
> AFAICS, the best way to achieve this is to include the ABI information in
> the version number of the linux-image metapackage.
Hmm. We need linux-modules metapackages than also. And it may be easier
to use virtual packages instead of versions. Something like:
| Package: linux-image-2.6-686
| Provides: linux-modules-2.6-686, linux-modules-latest-2.6.21-1-686
(normal)
| Package: linux-modules-2.6-xen-686
| Provides: linux-modules-latest-2.6.21-1-xen-686
(xen)
| Package: foo-modules-2.6-686
| Depends: linux-modules-latest-2.6.21-1-686
Otherwise broken down images like xen needs different handling from real
images. I don't want to do a real linux-modules for normal images.
Bastian
--
Genius doesn't work on an assembly line basis. You can't simply say,
"Today I will be brilliant."
-- Kirk, "The Ultimate Computer", stardate 4731.3
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
