Neil Tiffin wrote: > How do I handle the situation where the new release source file is > placed at a url (say "url a"), and the current release file is moved > from "url a" the to "url b"? "url b" does not include the newest > release, and the directory at "url a" not longer includes the old > release, so between the time of the new release and the update in > fink the source file URL does not work. > > This is psycopg2. > > url a = http://initd.org/pub/software/psycopg/psycopg2-2.0.5.1.tar.gz > url b = http://initd.org/pub/software/psycopg/PSYCOPG-2-0/ > psycopg2-2.0.5.tar.gz
Normally, such a short interim period is bridged by the presence of the source on the finkmirrors network. If you anticipate that this will happen again, you can make a CustomMirror field: Source: mirror:custom:%n-%v.tar.gz CustomMirror: << Primary: http://initd.org/pub/software/psycopg/ Secondary: http://initd.org/pub/software/psycopg/PSYCOPG-2-0/ << In this way, the user may get a wrong hit first, but the second one will then succeed. -- Martin ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Fink-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-devel
