Hi all, one more question which is ambiguous in the docs: The
documentation states If a package is listed in its own Conflicts, it
will be (silently) removed from that list.
However, many packages DO seem to put themselves into the Conflicts:
field. E.g. version 1.0.1 of package foo might
Philip Lamb wrote:
Hi all, one more question which is ambiguous in the docs: The
documentation states If a package is listed in its own Conflicts, it
will be (silently) removed from that list.
However, many packages DO seem to put themselves into the Conflicts:
field. E.g. version 1.0.1
On Thu, Sep 27, 2007 at 11:54:21AM +1200, Philip Lamb wrote:
Hi all, one more question which is ambiguous in the docs: The
documentation states If a package is listed in its own Conflicts, it
will be (silently) removed from that list.
What's ambiguous about that? If you list it, fink
