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 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. > ------------------------------------------------------------------------ A varianted package generally lists all possible variants (including itself) in Conflict/Replace if the variants can't coexist. I guess you could do conditionals, but that's more complicated.
Also, if you've changed the packaging, you may need to spell out some Conflicts/Replaces amongst the main packages and splitoffs. ------------------------------------------------------------------------- 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
