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 Message-ID: <00F8D6E8AB0DD3118F1A006008186C9607C851@server1.axonet.com.au> From: Andrew Dalgleish To: cygwin-developers AT sourceware DOT cygnus DOT com Subject: RE: next net release preliminary info Date: Thu, 27 Jan 2000 14:45:46 +1100 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain > -----Original Message----- > From: DJ Delorie [SMTP:dj AT delorie DOT com] > Sent: Tuesday, January 25, 2000 14:01 > To: cygwin-developers AT sourceware DOT cygnus DOT com > Subject: next net release preliminary info > [snip] > Pick the ones with the highest version number. [Andrew Dalgleish] Just a thought... I like the way debian number their packages with the "upstream" version as the most significant, and the "debian" version as the least significant. This makes it easy to identify which upstream version you are using, and also allows for more than one package version. One question: For packages like the GNU fileutils etc, will the source tarballs include the original source + patches (similar to debian) or pre-patched source files? I prefer the former because: Pros: * A stand-alone patch helps document what had to change to make the package work under cygwin. * A patch for version X will often (?) work for version X+1. * One package maintainer computes the diff vs many package downloaders doing it, perhaps incorrectly. Cons: * Harder to build. (And hence more noise on the list) * More work for the package maintainer. (Hmm, not good... :-) Regards, Andrew Dalgleish