On Tue, Nov 25, 2003 at 08:23:49PM -0800, Ben Hines wrote: > > On Sunday, October 6, 2002, at 01:16 PM, David R. Morrison wrote: > > >Conflicts: neon-ssl, neon, neon19, neon19-ssl, neon21, neon21-ssl, neon22 > >Replaces: neon-ssl, neon, neon19, neon19-ssl, neon21, neon21-ssl, neon22 > > Resend of oold message :) > > Every time we add a new neon package, we need to add that package > name to the Conflicts/Replaces line of EVERY OTHER neon package. > Would it be feasible to automate this? How about something like: > > SharedHeaders: neon > > automatically generates Conflicts: and Replaces: for every other > package with SharedHeaders: neon. > [...] Or maybe, it would be better to make it more general, even > > ConflictsReplaces: neon ? Conflicts/Replaces everything with the > ConflictsReplaces: neon line.
That field name seems confusing. It neither sets a Conflicts: neon or Replaces: neon, but instead provides and conflicts with others who provide the "neon" semaphor. Maybe "ProvidesExclusively:"? But hold on, hasn't dpkg already implemented a solution to this? Check http://www.debian.org/doc/debian-policy/ch-relationships.html section 7.3 and the therein-referenced section 7.5.2 (although a single-field shortcut might be nice to avoid typos and make it clear what the appearingly self-contradictory construct means:). dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
