On 2012-10-03 at 23:24:40 +0200, Markus Lude wrote:
> On Wed, Sep 26, 2012 at 09:24:26AM +0100, Stuart Henderson wrote:
> > On 2012/09/24 12:42, Adam Jeanguenat wrote:
> > >    To make life easier, Sourcefire provides a URL that works without
> > > respect to the automatically-incremented ID number for every file upload
> > > to snort.org: 
> > 
> > Ah good, they didn't used to have that. Diff against the committed
> > version, compared to yours it moves MASTER_SITES to the normal place
> > now it doesn't need to be updated per-release, moves SHARED_LIBS
> > to the normal place for daq, and doesn't use an unnecessary VERSION
> > variable.
> > 
> > OK with you Markus?
> > 
> > 
> > Index: snort/Makefile
> > ===================================================================
> > RCS file: /cvs/ports/net/snort/Makefile,v
> > retrieving revision 1.68
> > diff -u -p -w -r1.68 Makefile
> > --- snort/Makefile  26 Sep 2012 02:11:05 -0000      1.68
> > +++ snort/Makefile  26 Sep 2012 08:22:45 -0000
> > @@ -4,12 +4,7 @@ SHARED_ONLY =              Yes
> >  
> >  COMMENT =          highly flexible sniffer/NIDS
> >  
> > -# Original URL http://dl.snort.org/downloads/1862 redirects to a
> > -# time-limited Amazon S3 url. This would mean a bad distfile name.
> > -# The following hack allows it to work but XXX if updating, the
> > -# MASTER_SITES URL will need to be adjusted, not just DISTNAME.
> >  DISTNAME =                 snort-2.9.3.1
> > -MASTER_SITES =             http://www.snort.org/downloads/1862?/
> >  
> >  CATEGORIES =               net security
> >  
> > @@ -22,7 +17,10 @@ PERMIT_PACKAGE_CDROM =   Yes
> >  PERMIT_PACKAGE_FTP =       Yes
> >  PERMIT_DISTFILES_CDROM = Yes
> >  PERMIT_DISTFILES_FTP =     Yes
> > +
> >  WANTLIB =          c daq dnet m pcap pcre pthread z
> > +
> > +MASTER_SITES =             http://www.snort.org/dl/snort-current/
> 
> IIRC this URL is only valid until a newer version is released. The older
> tarball isn't available any more with this.

Not to worry; this should be okay. I tried several older versions before
recommending this change, as I also use it extensively in documentation.

I also just tried every release back to 2.9.0.4 (released Feb 2011)
using that URL scheme and each still points to the correct version.
Those are just redirects to the AWS storage, and more likely -- in my
experience -- to remain active than the previously-used URLs.

I'm not sure if they have a published retention policy for older
versions, but I would agree the '-current' in the URL is slightly
misleading.

    --avj

Reply via email to