On Sun, Sep 30, 2007 at 11:57:03AM -0400, Alexander K. Hansen wrote: > Max Horn wrote: > > Hi folks, > > > > unfortunately I made a serious mistake recently: I commited a version > > of my xchat package which should not yet have been commited, as it > > depends on GTK+2 2.10.0... > > > > So, I was wondering what to do now. Several possibilities come to mind: > > > > 1) Wait for GTK+2 2.10.0 -- well, unless it will come next week, this > > sounds like a bad plan :-) > > > > 2) Downgrade xchat.info to the previous version of the package -- > > easiest way, but could cause problems for people who already have > > 2.8.2 in their package database. Does our current index code cope > > with that just fine?
> I think 2) will be OK. At worst, people might have to do "fink index > -f" to force a rebuild of the cache. Concurred. The indexer *should* notice the "new" modification time on xchat.info and read it, replacing "whatever data it had from an older version of that file". Since nobody will have built xchat from the prematurely-committed file, nobody will have any trace of that version once the new old .info is committed, so no upgrade issues for users. dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
