Hi Max, my apologies. This only got half-implmented last night and I was going to send out an email after it was finished, but I can explain it now.
Our strategy for handling EOL for 10.4 is to place copies of all .info/.patch files into this 10.4-EOL subdirectory of finkinfo, and then to modify fink so that on 10.4 fink only sees those copies while on 10.5 and later, fink ignores those copies. (This will be implemented in fink-0.30.2 which is about to be released.) This way, people who are interested in using and/or supporting 10.4 can continue to do so, but in their own area which won't affect the later distributions. There is an overhead for users, of course, who are getting extra copies of .info/.patch files, but I expect those will mostly be static. All of the other strategies we thought of has worse overhead for users or maintainers. As for 10.7, there is still an ongoing debate about whether 10.7 should continue to use the "10.4" directory or start a new one. This bifurcation will actually make it a lot easier to use 10.7 with the old directory, since we can now remove OS X 10.4-specific versions of packages. (For example, we might currently have foo.info and foo-10.6.info with the former handling both 10.4 and 10.5; this can now be switched to foo-10.5.info and foo.info with the latter handling both 10.6 and 10.7.) -- Dave On Jul 11, 2011, at 2:09 AM, Max Horn wrote: > Hi there, > > just did a "cvs up" on my fink dists checkout, and it added tons of "new" > (well, copied) files in > 10.4/stable/main/finkinfo/10.4-EOL > and > 10.4/unstable/main/finkinfo/10.4-EOL > > There were some discussions on abandoing 10.4 support and also on how to deal > with 10.7, but I can't find anything in my mail archives on 10.4-EOL. > > So, could somebody please explain the rationale behind this, and how fink > package maintainers are supposed to deal with it? > > > Bye, > Max > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > _______________________________________________ > Fink-devel mailing list > Fink-devel@lists.sourceforge.net > List archive: > http://news.gmane.org/gmane.os.apple.fink.devel > Subscription management: > https://lists.sourceforge.net/lists/listinfo/fink-devel ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net List archive: http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
