On Sep 29, 2006, at 2:19 AM, Martin Costabel wrote:

> 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
>

How do I know if a file is available on the mirror?  If the file is  
not on the mirror, how can it be or does it get added?

For example my .info is currently

# Unpack Phase:
Source-MD5: 052e4b97dab47708fdcdc36ffb25af66
Source: http://initd.org/pub/software/psycopg/psycopg2-%v.tar.gz

I see how the above could work.  But if psycopg is not on the mirror  
it will always fail the first time.

Neil


-------------------------------------------------------------------------
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

Reply via email to