Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!ucsd!ncr-sd!greg
From: greg@ncr-sd.SanDiego.NCR.COM (Greg Noel)
Newsgroups: comp.sources.d
Subject: Re: "Archive-name:" proposed change
Keywords: multiple part postings
Message-ID: <1187@ncr-sd.SanDiego.NCR.COM>
Date: 28 Mar 89 22:06:15 GMT
References: <780@usl.usl.edu> <2464@ndsuvax.UUCP>
Organization: NCR Corporation, Rancho Bernardo
Lines: 27

In article <780@usl.usl.edu> pml@usl.usl.edu (Patrick Landry) writes:
>My proposal would be to add a number to the end of the
>Archive-naem [sic] header such as
>       Archive-name: foo/bar/Part01of25

In article <2464@ndsuvax.UUCP> ncoverby@ndsuvax.UUCP (Glen Overby) writes:
>... all you're changing is the last
>filename element of the Archive-Name line.  This might be nice, but I get
>the feeling that it would make things a bit more cluttered.

I'd like to see it become even more "cluttered" -- I'd like to see the
version identifier and the classification be included as part of the
archive-name.  That is, if the posting is, say, a revised version of a
previously-posted game of hangman, the archive-name might be:
	Archive-name: fun/hangman/V01r01-src/Part01of03
(I could imagine that the classification could be even more articulated.)
This way, not only do the pieces of the program end up associated, but
bug fixes and patches could be posted to the same location, thus keeping
them together as well.  Suffixes of src, bin, and doc could be attached
to the version specifier to separate particular components of the package.
And it would keep programs of a similar nature together, so that if you
wanted to look for all the games (or to ignore all the games), that could
be automated as well.

That's a rather messy paragraph, but I think you get the general idea.
-- 
-- Greg Noel, NCR Rancho Bernardo   Greg.Noel@SanDiego.NCR.COM  or  greg@ncr-sd