On 9/14/2014 6:11 AM, Thomas D. wrote: > Hi Tom, > > You wrote: >> Our convention is that when a new version is released, the prior release >> is moved into the 'superseded' directory. > > That's a real problem for us. > > I am suggesting the following change: > > 1) > http://www.shorewall.net/pub/shorewall/4.6/shorewall-4.6.3/superseded/ > > should become > > http://www.shorewall.net/pub/shorewall/4.6/shorewall-4.6.3/archive/ > > 2) > All files should be dropped in "archive". > > 3) You may want to symlink the latest version if you want to keep a > clean download directory with the latest version: > > http://www.shorewall.net/pub/shorewall/4.6/shorewall-4.6.3/shorewall-core-4.6.3.3.tar.bz2 > -> archive/shorewall-core-4.6.3.3.tar.bz2 > > > This way we would always have a stable URI. The suggested change is > small and shouldn't break any existing setup.
I'm moving this discussion onto the development list, given that changes to the layout of the ftp site potentially affect all distribution maintainers. Thomas is complaining that URIs in the FTP site are transient, given that files move into the superseded directory when they are superseded. -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________ Shorewall-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-devel
