the fate of firewire

Axel Thimm Axel.Thimm at ATrpms.net
Tue Sep 14 07:35:13 UTC 2004


On Tue, Sep 14, 2004 at 08:49:27AM +0200, Arjan van de Ven wrote:
> On Tue, 2004-09-14 at 00:27, Rik van Riel wrote:
> > On Mon, 13 Sep 2004, Thorsten Leemhuis wrote:
> > > Am Montag, den 13.09.2004, 16:47 +0200 schrieb Arjan van de Ven:
> > 
> > > > I can't package that right so I rather don't.
> > > 
> > > Just out of curiosity, could you give me one or to details on the
> > > problem(s)? Thanks.
> > 
> > Installing a new kernel won't automatically get a new
> > kernel-firewire package installed.  This breaks setups where
> > people forget to update the kernel and will certainly break any
> > automatic upgrades people may have set up.
> 
> it's even worse, say you want to install an OLDER kernel for whatever
> reason; just "newest external" won't cut it with the way most of these
> are packages; you need the exact matching one.

That's now an old problem in kernel-module packaging which has been
solved a year ago. Just place the kernel's version/release into the
kernel module rpm's name like

kernel-module-firewire-2.6.8-1.521-2.6.8-1.521

and set up struct dependencies to the matching kernel. Doesn't solve
the extra install stepp, but you won't get bitten by downgrades,
concurrent kernel installs and so on.

> and you need it installed before the kernel gets installed, so that it
> makes the initrd. 

If you want to support booting from firewire there is no sense in
splitting any sub-package off. firewire won't be optional.
-- 
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/fedora-devel-list/attachments/20040914/e7ea2063/attachment.sig>


More information about the fedora-devel-list mailing list