Max Horn <[EMAIL PROTECTED]> wrote: > At 14:44 Uhr -0700 06.10.2002, 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 > > > > > >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. > > Hm? I think it is sufficient to have the full list in the newest > neonXY. If neon23 conflicts with neon22, there is no need to make > neon22 also conflict with neon23, as conflicts obviously go into both > directions anyway. >
There is a difference with the Replaces field. You need to have this in both header packages, because users may need to switch between neon22 and neon23 to build different other packages, and the packages both need the "Replaces" field so that this works. -- Dave ------------------------------------------------------- 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
