Date:	Tue, 23 Jun 1998 14:47:17 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	Vik Heyndrickx <Vik DOT Heyndrickx AT rug DOT ac DOT be>
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: [fdonahoe AT wilkes1 DOT wilkes DOT edu: Patch Level in /v2gnu]
In-Reply-To:	<358F8B1E.44F3@rug.ac.be>
Message-ID:	<Pine.SUN.3.91.980623144022.17359C-100000@is>
MIME-Version:	1.0

On Tue, 23 Jun 1998, Vik Heyndrickx wrote:

> And I can imagine that there are naive users that download the plain
> file *and* the symlinked archive file, so... back to square one.

No, I meant that a user who sees gcc281b.zip and gcc281b-patch-1.zip 
might download the former.  So I suggest that gcc281b.zip would be a 
symlink to the highest patch-level.

> Neither do I, but the whole point is that we need something different
> than the date/time to distinguish between re-releases without breaking
> the gnu version number equivalences.

If I understand Frank's idea, it was because he wants to be able to know, 
from the file name alone, whether he has the latest build.  So, if he has 
downloaded gcc281b-patch-2.zip, and he sees gcc281b-patch-5.zip, he will 
immediately realize that a new binary is available.  (This, of course, 
assumes that he remembers what was the last patch-level he downloaded, 
which might be tricky if the name was truncated to 8+3 on the target 
machine.)

> What file would you choose (you might have the opportunity to see the
> file size and date).

*I* would be confused and try to find a README which explains what should 
I do.  What the naive users will do is anybody's guess.

Size and date aren't helpful, apparently, or else we wouldn't be having
this dicussion. 

- Raw text -