On Mon, Jan 26, 2004 at 08:41:08PM -0500, David R. Morrison wrote:
> > So how do you feel about the .vinfo solution?
>
> Could you explain that a bit more? I didn't quite follow...
Consider foo-pm.info, which includes "Package: foo-pm%Q". This file is
not compatible with any current version of fink. If such a .info
exists on a user's system, fink will crash during indexing ("unknown
expansion in Package").
Let's say a new fink is released which does support %Q. As soon as a
user selfupdates, his fink will be upgraded and from then on he'll be
able to index these new .info files. But if a new-style .info is added
to CVS before he's updated his fink, he's screwed. Selfupdate will
pull the .info for the new fink and the new-fangled .info, he can't
even get as far as upgrading his fink (since he's gotta have his old
fink reindex to even know there *is* a new fink).
What is needed is a way to totally hide certain .info files from
versions of fink older than a certain version. So I proposed putting
anything that uses %Q in Package go in a .vinfo. Because they're not
".info", they're invisible to old-fink. But new-fink (which knows how
to handle them) would also know to look for them.
It's not the prettiest of hacks, but it was a probably-workable
solution that came to mind...
dan
--
Daniel Macks
[EMAIL PROTECTED]
http://www.netspace.org/~dmacks
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
