OoO Lors de la soirée naissante du samedi 17 mai 2008, vers 17:57, Armin
Berres <trigger@space-based.de> disait:
> Replaces must not come with Conflicts.
> Consider a package foo which contains a lot of architecture independent
> files. One day you decide to split the arch independent files into a new
> package foo-data. foo-data will replace the old foo package, but there
> is no need to conflict with it.
Even against older versions? You have one package foo-0.5.2-1, you split
it in foo-0.5.2-2 and foo-data-0.5.2-2. Should not foo-data-0.5.2-2
conflicts with foo (<= 0.5.2-1)? This is not a very realistic example
because in this case, I suppose that foo will depend on foo-data (=
${binary:Version}).
Thanks for any insight.
--
printk(KERN_ERR "msp3400: chip reset failed, penguin on i2c bus?\n");
2.2.16 /usr/src/linux/drivers/char/msp3400.c
Attachment:
pgp6kgA7fouFb.pgp
Description: PGP signature