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 :)
This is a bit silly.. 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.
Problems pogma noted: This changes the deb. So, when you add a new package with this field, as before you still need to remember to rev up all those packages. Still, changing one number is less of a pain. And this is cleaner certainly, in the info file.
-Ben
------------------------------------------------------- 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
