On 17 Mar 2010, at 01:44, Daniel Macks wrote: > On Tue, Mar 16, 2010 at 11:39:35AM +0100, Max Horn wrote: >> [...] >> >> E.g. our old "gettext" package is not even marked obsolete, and if >> I was looking for gettext, well, it would be the first thing for me >> to see... :) Don't get me wrong, I am not asking for it to be >> marked as such. I just want to point out that it's not trivial for >> a maintainer to figure out that they shouldn't use it. > > Nit: "an old libversion" is not a candidate for the > fink-obsolete-packages mechanism because nothing literally and > transparently replaces it. But could definitely add DescUsage (that > nobody probably reads).
But would it not be possible to have a clone of "fink obsolete packages" that would do the same _ warning at least anybody running "fink -m" _ for any version of some pkg (upstream, not in fink's sense) that is superseded by something newer ? There are too many gettext-like pkgs to handle this on a case-by-case basis... The corresponding db should ideally come from declarations in info files that this pkg supersedes A, B, C ..; but could possibly, as a provisional transition measure, be put into some separate, manually maintained file. JF ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Fink-devel mailing list [email protected] http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
