On Fri, Dec 3, 2010 at 4:51 PM, Loïc Minier email@example.com wrote:
On Fri, Dec 03, 2010, Dave Martin wrote:
Having "latest" or "current" aliases can cause traceability problems if having mirrored the files, you can't determine which actual build/release it was.
We can include a build id in the image itself to help with this; we can also keep a map of MD5SUMs for past images to help with this as well
Is it possible to have an easily-parsed file /LATEST or /CURRENT which just contains the URL(s) of the latest image(s)? -- tools or scripts can trivially download those files to get the right canonical URLs for the newest images at any particular time, without having to guess.
A script could use this, but it means you always have to use a wrapper; you can't e.g. use rsync directly
True--- as long as we have some way to provide the traceability / reproducability, I'm happy.