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

[Michael C. Shultz]

On Friday 12 November 2004 12:50 pm, Frank Laszlo wrote:
> Norikatsu Shigemura wrote:
> >On Fri, 12 Nov 2004 13:10:19 -0500
> >
> >Frank Laszlo <laszlof at vonostingroup.com> wrote:
> >>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
> >
> > Author hopes to update and build *almost daily*.  So he
> > didn't remain old archives.
> >
> >>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.
> >
> > To update is not so hard.  So tell me it is updated. OK.
> >_______________________________________________
>
> I cant think of a way to automate this within the port. I can make
> the port fetch the distfile depending on the date.. like this:
>
> PORTVERSION=    ${MYDATE}
> DISTNAME=       live.${PORTVERSION}
> MYDATE!=        date "+%Y.%m.%d"
>
> But the problem exists with the distinfo. The file size and md5
> checksum will change daily, isnt there a NO_CHECKSUM or something
> within the port? Thanks!
>
> Regards,
>     Frank Laszlo

You can remove the distinfo file then it will fetch but what about the 
random "a's" being added to the port name?  I personally would like to 
see a copy of the distfile maintained on another site then updated at
a more reasonable time interval.

-Mike