From: "Matthias Wächter" <matthias.waechter@tttech.com>
Subject: Re: Version Numbers in Download File Names
Date: Wed, 12 Jul 2006 14:37:34 +0200 [thread overview]
Message-ID: <44B4ED0E.1040104@tttech.com> (raw)
In-Reply-To: <44B4E24E.8090706@elvenkind.com>
Taco Hoekwater schrieb:
> Matthias Wächter wrote:
>> Is there a strong motivation against having versioned package file names,
>> possibly with some months/years of history?
> > Or is this archive available but I am unable to find it? ;)
> There is an archive of old releases and file versions on-line,
> but at a different location. Check this page as a starting point:
> http://wiki.contextgarden.net/Revisions
Taco, thanks for pointing me there and indirectly to the releases and SVN repository at supelec.fr. Stupid /me didn't search the garden for it.
Two comments nevertheless.
https://foundry.supelec.fr/frs/?group_id=14 gives me quite some versions of Context, but the download paths for each precise version is not related to the release date or the SVN revision, for example, the 20060609 release can be downloaded as https://foundry.supelec.fr/frs/download.php/305/cont-tmf.zip. Can't it be something like https://foundry.supelec.fr/frs/download.php/cont-tmf-20060609.zip, or in case of true SVN snapshots maybe https://foundry.supelec.fr/frs/download.php/cont-tmf-164.zip having '164' as the associated SVN repository revision number? That would be easy to maintain in subsequent application packages for Context. Certainly, supelec.fr and gforge.org have the last word on this issue. Anyway, thanks for the link, it is a big step towards a solution.
Second: I tried to checkout the repository anonymously as mentioned on https://foundry.supelec.fr/scm/?group_id=14 without success (it asks me for username/password). Either anonymous read-only access should be enabled as documented, or the documentation on this page should change (but why should the repository be publicly browseable as well as versioned snapshots be publicly available without proper public Subversion access?). In case cont-tmf.zip is a simple consistent snapshot of the (then) publicly available SVN repository, the problem of versioning would vanish in a second, I'd just have to refer to the associated SVN revision of the tree.
Thanks,
- Matthias
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
next prev parent reply other threads:[~2006-07-12 12:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 11:20 Matthias Wächter
2006-07-12 11:51 ` Taco Hoekwater
2006-07-12 12:37 ` Matthias Wächter [this message]
2006-07-12 13:18 ` Taco Hoekwater
2006-07-12 16:04 ` Matthias Wächter
2006-07-12 17:27 ` Taco Hoekwater
2006-07-13 14:26 ` Hans Hagen
2006-07-13 13:37 ` Hans Hagen
2006-07-12 13:01 ` Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44B4ED0E.1040104@tttech.com \
--to=matthias.waechter@tttech.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).