net/liveMedia live.2004.11.11.tar.gz not fetchable agian

[Frank Laszlo]

Michael C. Shultz wrote:

>>Michael C. Shultz wrote:
>>On Friday 12 November 2004 09:10 am, you wrote:
>>    
>>
>>The DISTNAME is obviously wrong. Maybe live.com decided to change
>>their naming scheme.
>>
>>Regards,
>>    Frank Laszlo
>>    
>>
>
>Here are other liveMedia files from my ports/distfiles directory.  The 
>name liveMedia live.2004.11.11.tar.gz seems consistant.....
>
>/usr/ports/distfiles/live.2004.09.02.tar.gz     /usr/ports/distfiles/live.2004.10.26.tar.gz
>/usr/ports/distfiles/live.2004.10.11.tar.gz     /usr/ports/distfiles/live.2004.10.28a.tar.gz
>/usr/ports/distfiles/live.2004.10.14.tar.gz     /usr/ports/distfiles/live.2004.11.01.tar.gz
>/usr/ports/distfiles/live.2004.10.18.tar.gz     /usr/ports/distfiles/live.2004.11.02.tar.gz
>/usr/ports/distfiles/live.2004.10.19.tar.gz     /usr/ports/distfiles/live.2004.11.09a.tar.gz
>/usr/ports/distfiles/live.2004.10.22.tar.gz
>
>
>  
>
Not exactly, as you can see there is a couple with an 'a' after it.

 /usr/ports/distfiles/live.2004.10.28a.tar.gz
 /usr/ports/distfiles/live.2004.11.09a.tar.gz

Michael Johnson has informed me that this means there is multiple 
releases in the same day. Maybe the port should address this? Also, I 
see that DISTNAME is statically set, and if infact live.com creates 
build daily and doesnt archive old builds, this needs to be updated to 
reflect the current date in the DISTNAME to retrieve the proper 
distfile. If the maintainer is unresponsive, I would be willing to write 
a patch for this. Hope this helps.

Regards,
    Frank Laszlo