On Mon, Jan 26, 2004 at 02:14:00PM +0900, Peter O'Gorman wrote: > Daniel Macks wrote: > | > | In implementing variants, I'm doing some percent expansions on Package > | using %things that may not be known to previous fink. That means (I > | think) that if a user selfupdates while running an older fink and > | there are variant-ish .info files, his fink is gonna croak when it > | tries to index (he's still under old-fink, since it's not yet known > | that there is a new fink package). > > Well, don't commit anything to unstable until a fink which understands the > new % expansions has been released. Then when the user selfupdates fink will > install the latest fink and reexecute fink before creating the index.
I was wondering about that approach. I wasn't sure if I could assume a user will never be upgrading from more than one fink version old. So how do you feel about the .vinfo solution? 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
