X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
From: Juan Manuel Guerrero <juan DOT guerrero AT gmx DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: ANNOUNCE: release 3 of the DJGPP port of GNU grep 2.5.3 uploaded.
Date: Wed, 23 Jan 2008 04:08:04 -0800 (PST)
Organization: http://groups.google.com
Lines: 51
Message-ID: <27d1396a-7456-4a20-950b-22214ca9526c@h11g2000prf.googlegroups.com>
References: <200801202022 DOT m0KKMLg0001310 AT delorie DOT com> <47941ACF DOT B8EBD95B AT yahoo DOT com> 
	<4c6759dd-f536-49ea-8d8b-a2feb5192d77 AT f47g2000hsd DOT googlegroups DOT com> 
	<47956051 DOT 2DB8A290 AT yahoo DOT com> <29237ff0-179d-4d5a-a41c-45da1e35999a AT i12g2000prf DOT googlegroups DOT com> 
	<200801222057 DOT m0MKv39r017880 AT envy DOT delorie DOT com> <47967CB4 DOT 493C0E1C AT yahoo DOT com>
NNTP-Posting-Host: 88.68.34.78
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Trace: posting.google.com 1201090084 4092 127.0.0.1 (23 Jan 2008 12:08:04 GMT)
X-Complaints-To: groups-abuse AT google DOT com
NNTP-Posting-Date: Wed, 23 Jan 2008 12:08:04 +0000 (UTC)
Complaints-To: groups-abuse AT google DOT com
Injection-Info: h11g2000prf.googlegroups.com; posting-host=88.68.34.78; 
	posting-account=OsAajgoAAADdKJnkJkmhzqP0jo6I_P_0
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-us) 
	AppleWebKit/48 (like Gecko) Safari/48,gzip(gfe),gzip(gfe)
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

CBFalconer schrieb:
> DJ Delorie wrote:
[snip]
> > As for the naming conventions... you've been doing a lot of work
> > on ports, I think you've earned the right to decide how it's done.
>
> I'm not worrying about goodness or badness.  To me, the point is
> that his uploads are destroying previous work.  They also prevent
> tracking the changes made.  We all know that bad ports are possible
> and do occur, and thus need correction.  But just reloading the
> same file name doesn't allow the user to detect it, except possibly
> by detailed examination of the exact file dates.

I am aware of this.  That is the reason why I always mention the
timestamp of the uploaded zip file in the announcement.  Most
of the mayor DJGPP mirrors update in 24h so that the announcement
together with the timestamp, the dsm file and the diffs file
should be information enough for the user to know that something
has changed and what has changed.
Most of the zip files are ports.  In most of the cases there will be
only
one release, in the worst one or two more to fix something so I
insist that there is no reason to keep previous releases.  The ports
of grep and splint are very good examples that broken old releases
must be replaced and retired.  All new releases of ports I have
produced are bug fixes and not extensions of the functionality
provided by the ported program so there is no reason to keep
the previuos release available to the user.

Neitherless, if DJ do not object I would suggest to change the
actual naming convention and adopt one similar to the one
that uses cygwin.  This is something like this:
  foobar123-1[bsd].zip
or
  foobar20080123-1[bsd].zip
The first means th package name followed by the version
number followed by release number (1 in this case).   We also
keep the b,d and s letters to code the type of package content.
The second version is for CVS checkouts or something similar
where the checkout timestamp is used as version number.
Suggestions, objections, comments are welcome.

I still insist that broken old releases must be retired.  I do not
want to have to answer user questions like "which one
of the releases is the better one?" or "what shall I download?".


Regards,
Juan M. Guerrero