Martin Costabel <[EMAIL PROTECTED]> said: > David Reiser wrote: > [] >> what's a good way to deal with the fact that as soon as there's another >> official revision, I'm likely to want that one instead of my hack? If I >> bump the revision up by 1, then it will conflict immediately. If I bump >> it up a lot, doesn't my revision interfere with access to the new >> versions from the normal maintainer? > > For your private variants of revision r you can use r.0 r.1 etc. In > dpkg's arithmetic, r < r.0 < r+1.
Also, place your modified .info file (and the .patch file it uses, it any) in /sw/fink/dists/local/main/finkinfo instead of editing the one in unstable/ (and make sure 'local/main' is in the Trees line of your /sw/etc/fink.conf file). The selfupdate process often refuses to overwrite files that have been locally modified--by working in a tree that fink uses but selfupdate doesn't touch, selfupdate will bring you a new .info when it gets released. dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Fink-beginners mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-beginners
