carey@m.cs.uiuc.edu (01/13/90)
One question-- are the archive sites (the distribution sites announced in the release announcement) going to have the same stuff? It seems like there should be an automatic update done daily to keep everything the same. At the archive sites, there is now a contrib and an oldcontrib. From previous notes, I am pretty sure that there are versions of clients newer than the distribution that are not in contrib (although they might have gotten moved to oldcontrib). Everyone ought to get their new versions into contrib. Has any thought gone into a master README file? Something like-- Client R4-dist version Current version File-name Contact ------ -------------- --------------- --------- ----------- xlaunch 4.0 4.5 xlaunch.tar.Z bob@zit.edu xlaunch-patches -- 4.6 xlaunch.4.6patches.tar.Z bob@zit.edu PEX -- alpha1.0 pex.randd.edu:pexalpha1.0.tar.Z Yes, you can get information from an ls listing, but it is a lot of guesswork. A more complete readme file, giving a short description of each contribution might be nice. This might be a little work to set up, but it would cut down on the ftp traffic by a lot. Plus save everyone a lot of work.
rws@EXPO.LCS.MIT.EDU (Bob Scheifler) (01/13/90)
are the archive sites (the distribution sites announced
in the release announcement) going to have the same stuff?
I am not aware of any coordinated effort to do this.
Has any thought gone into a master README file?
That would imply some kind of central coordination. We at MIT make
disk space available as a public service, but we don't have the
resources to commit people towards maintaining the contrib area.
Other archive sites will have to speak for themselves.jim@EXPO.LCS.MIT.EDU (Jim Fulton) (01/15/90)
One question-- are the archive sites (the distribution sites announced
in the release announcement) going to have the same stuff?
One thing to keep in mind is that the user-contributed tapes (under ./contrib/
in R4) have no direct relationship to the ~ftp/contrib/ area on expo. The
sites listed in the announcement are archiving R4, but probably are not trying
to grab expo's ~ftp/contrib/ tree.