Date:	Thu, 10 Dec 1998 11:14:08 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Alessandro Pisani <alextxm AT tin DOT it>
cc:	djgpp AT delorie DOT com
Subject:	Re: DJGPP 2.02/GCC 2.8.1 PROBLEM - it was my fault
In-Reply-To:	<Version.32.19981209205710.00dcc940@box1.tin.it>
Message-ID:	<Pine.SUN.3.91.981210111317.1269F-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com

On Wed, 9 Dec 1998, Alessandro Pisani wrote:

> why don't you change also the version num
> (like 2.8.1.1 or 2.8.1a or 2.8.1plX (patch-levelX) etc) when you re-update
> a fixed version of a package ?

We can't change the version numbers of GNU packages, as it would
create a terrible confusion.  For example, if you call a patched
version 2.8.1.1, and the GNU maintainers release their version with
the same number, what do we do then?

Also, longer version names, like 2.8.1.plX, which could help the above
problem, are impossible because the zip file names have to fit into
the DOS 8+3 limits.

The drill is to watch the announcements of updated uploads and
upgrade.

Of course, everyone who ports a package tries to do their best to
avoid bugs which will need a new upload, but bugs do happen...

> I have another question: ar can merge two libs (foo.a and foo2.a) togheter

No, you need to extract all the object files from one library (with
the x command), then add them to the other (with the r or q command).

- Raw text -