ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Matthias Wächter" <matthias.waechter@tttech.com>
Subject: Version Numbers in Download File Names
Date: Wed, 12 Jul 2006 13:20:01 +0200	[thread overview]
Message-ID: <44B4DAE1.3040800@tttech.com> (raw)

Hi!

Pardon me for requesting more support from pragma-ade prior to ever using the mailing list for general support questions. Maybe I should post this one directly to Hans but others might be interested in this issue as well.

Despite my little but growing knowledge of Context I am currently evaluating its suitability for document building in our company (our workflow is currently Latex-based). A prime aspect of our company's work is to follow well-defined processes, and as part of that, we have to be able to refer to specific versions of applications that are used in the development of our projects. When used, this would apply to Context as well.

Obviously, downloading from pragma-ade gives version numbers only on the entry pages like http://www.pragma-ade.nl/download-1.htm next to the links to the files, but the package files themselves like http://www.pragma-ade.nl/context/current/cont-tmf.zip don't have versioned names (not mentioning that Context and its modules actually _do_ report version numbers as dates upon use).

Is there a strong motivation against having versioned package file names, possibly with some months/years of history? Has this support feature ever been considered by pragma-ade or asked for by their (non-)paying customers? Or is this archive available but I am unable to find it? ;)

Just an example:

Instead of
http://www.pragma-ade.nl/context/current/cont-tmf.zip

use a browseable directory like http://www.pragma-ade.nl/context/archive/ containint files like
http://www.pragma-ade.nl/context/archive/cont-tmf-20060518.zip
http://www.pragma-ade.nl/context/archive/cont-tmf-20060601.zip
http://www.pragma-ade.nl/context/archive/cont-tmf-20060629.zip

and possibly set /context/current/cont-tmf.zip as an internal file system link to the latest file in /context/archive/ for those interested only in the latest version. The proposed method could be applied to all other download files as well.

That way and as long as the archive files are available, a precise version of Context could be fetched from pragma-ade's server without maintaining a local versioned archive of cont.tmf.zip etc. Referral to a specific version of Context would be a lot easier, and documenting the tools used for a project would be a lot simpler. A common understanding of a Context version, reflected in its package file name, would reduce the effort of those responsible for local version control and install package maintenance.

Thanks,
- Matthias

             reply	other threads:[~2006-07-12 11:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-12 11:20 Matthias Wächter [this message]
2006-07-12 11:51 ` Taco Hoekwater
2006-07-12 12:37   ` Matthias Wächter
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=44B4DAE1.3040800@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).