However, many packages DO seem to put themselves into the Conflicts: field. E.g. version 1.0.1 of package foo might list Conflicts: foo (< 1.0.1-1). This would seem to be redundant, since the upgrading of a package would naturally remove the older version.
So, under what circumstances should a package list itself on the Conflicts: line?
Regards, Phil.
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________ Fink-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-devel
