home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!moe.ksu.ksu.edu!ux1.cso.uiuc.edu!news.cso.uiuc.edu!ehsn11.cen.uiuc.edu!jy10033
- From: jy10033@ehsn11.cen.uiuc.edu (Joshua M Yelon)
- Subject: Obsolete files at archive sites.
- Message-ID: <BxtE77.1By@news.cso.uiuc.edu>
- Sender: usenet@news.cso.uiuc.edu (Net Noise owner)
- Organization: University of Illinois at Urbana
- Date: Mon, 16 Nov 1992 15:11:29 GMT
- Lines: 19
-
- There are a lot of obsolete files at the archive sites (I'm not blaming
- anybody, it's just a natural consequence of fact that Linux is developing
- very rapidly). The obsolete files do cause a lot of confusion, though...
-
- Perhaps we could set up some sort of 'version control'. Here's one
- possible approach: when you download a package, you could see if it works
- with the currently-accepted version of linux and associated utilities.
- If not, you could send me a mail message with a subject line like this:
-
- BROKEN: tsx-11.mit.edu:/pub/linux/sources/usr.bin/admutil1.2
-
- I could compile these into coherent listings, and mail them to the
- archive maintainers on a weekly basis. The archive maintainers could
- respond by moving the files to a 'possibly-bogus' subdirectory.
-
- That's just a top-of-my-head solution... if you have something better,
- by all means, suggest it. I do think it's important, though, that
- we sort things out a little bit.
-
-