Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Date: Thu, 20 Apr 2000 09:19:06 -0400 Message-Id: <200004201319.JAA29390@envy.delorie.com> From: DJ Delorie To: m DOT ring AT ndh DOT net CC: cygwin-developers AT sourceware DOT cygnus DOT com In-reply-to: (message from Michael Ring on Thu, 20 Apr 2000 10:36:41 +0200) Subject: Re: How to find out if something has changed in the latest directory References: > Also the cygwin directory has changed and also tcltk. I changed the directory permissions, not the contents. > After browsing the list I did not find any clue to a new cygwin > version and perhaps a clue that only the md5.sum was regenerated. Cygwin was not updated. > In the past I also found out that sometimes files in the 485-snapshot > subdirectories changed in size but the directory itself kept the old > date. Yup, that's the Unix way. > This does not make it easy to quickly find out if a file has changed. File name and time stamp are the way. > Perhaps an information could be posted to cygwin-announce (or cygwin) > everytime that something has changed in the distribution. If posting a It is! Nothing changed! > Perhaps a small script could be used to make sure that the > directory-date reflects the date of the newest file in a subdirectory. Hmmm, interesting idea, but I wonder what it would do to the mirror programs? > Invent version numbers! Files could be named like that: > bash-2.03-1-cygwin-bin.tar.gz Gee, WE DO THAT. It was discussed long ago, and we all agreed to use that system, and we do. Or, at least, we will for all new releases; the ones from the cdrom don't really have version numbers.