Re: Updating the website on point releases
On Mon, Dec 16, 2013 at 02:39:01PM -0400, David Prévot wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA256
>
>[ Adding press@ if they wish to comment on the proposal. ]
>
>Le 16/12/2013 11:44, Andrei POPESCU a écrit :
>> On Lu, 16 dec 13, 15:22:07, Steve McIntyre wrote:
>>>
>>> Thoughts?
>>
>> Why not change the links to use the 'current'[1] symlink?
>
>That’s what we already do for the Live images, but the main links point
>to specific files containing the version number. E.g. on the main page:
>
>http://cdimage.debian.org/debian-cd/7.3.0/multi-arch/iso-cd/debian-7.3.0-amd64-i386-netinst.iso
>
>If a symlink could also be provided on cdimage side to the files we
>need, it would probably be a worth considering solution (no delay, links
>“always” up).
I'm bothered about having too many symlinks in place in a visible
directory (e.g. inside iso-cd/iso-dvd etc.), as they'll obscure the
actual contents too much. Hmmm, maybe...
At the moment, we have a top-level symlink:
current -> 7.3.0/
7.3.0 then contains all the files underneath. I *could* switch that
over to having "current" be an actual directory tree, with "current"
links to the files under 7.3.0:
current/
/i386/
/iso-cd/
debian-latest-i386.iso --> ../../../7.3.0/i386/iso-cd/debian-latest-i386.iso
etc. I can script producing that symlink tree so it'll be essentially
instantaneous. The _downside_ to this is that people will end up
downloading ISO files with filenames that can't/won't match anything
real. When people come to try to validate what they've got with
checksums, or (worse!) try to report bugs, that's going to bite us
too.
>If not, I’d be happy to see the debian-cd people join the
>press group (or let the DSA create a specific group giving them the
>needed rights) allowing them to trigger an effective partial rebuild
>(and I’d also be happy if the non official press helpers doing the
>announcement work – e.g. Cédric Boutillier and Paul Wise – could be
>added to the press group if they wish to).
This would be the best solution, I think. So long as we're not going
to be bitten by caching issues like we've seen in the past.
Other option: redirect via a CGI/whatever dynamic to map "latest" into
the real path/filename on demand.
--
Steve McIntyre, Cambridge, UK. steve@einval.com
"You can't barbecue lettuce!" -- Ellie Crane
Reply to: