Il giorno gio, 27/07/2006 alle 00.22 +1000, Hamish Moffatt ha scritto:
> Now extend for more than two packages. Should each package list every
> other, require every package to be updated when another is added?
>
> Instead they can all provide and conflict a common virtual package.
It is ok to conflict on a common virtual package, but I don't see the
point for a package conflicting with itself. If there are other packages
which provide it, then it's up to them to conflict with the real one and
we are not talking about **virtual** packages anymore.
Another example:
* foo
* foo-extended: provides foo, conflicts foo;
* foo-extended-nosql: provides foo, conflicts foo;
Is it really needed for foo to conflict with itself to have foo-extended
or foo-extended-nosql uninstallable in parallel with it? Aren't their
conflicts enough?
--
Fabio Tranchitella <kobold@debian.org> .''`.
Proud Debian GNU/Linux developer, admin and user. : :' :
`. `'`
http://people.debian.org/~kobold/ `-
_____________________________________________________________________
1024D/7F961564, fpr 5465 6E69 E559 6466 BF3D 9F01 2BF8 EE2B 7F96 1564
Attachment:
signature.asc
Description: Questa =?ISO-8859-1?Q?=E8?= una parte del messaggio firmata digitalmente