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 This is getting a bit silly.. and now, neon23 is on the tracker. 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. Then we wouldn't have to update EVERY neon headers package every time there is a new major version of neon. Or maybe, it would be better to make it more general, even ConflictsReplaces: neon ? Conflicts/Replaces everything with the ConflictsReplaces: neon line. -Ben ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
