Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <006b01c17f90$db687a00$0200a8c0@lifelesswks> From: "Robert Collins" To: "Charles Wilson" , "Jan Nieuwenhuizen" Cc: "Gerrit P. Haase" References: <878764062.20011128173421@nyckelpiga.de> <4434079433.20011129221637@familiehaase.de> <9517228633.20011203135833@familiehaase.de> <3C0D8535.D67735D1@ece.gatech.edu> <3C0EAD6B.AD71A7EB@ece.gatech.edu> Subject: Re: experimental texmf packages Date: Sat, 8 Dec 2001 13:34:26 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 08 Dec 2001 02:34:23.0100 (UTC) FILETIME=[D8B763C0:01C17F90] ----- Original Message ----- From: "Charles Wilson" > > You'd want a central tool(set) to do the > > building and packaging, and package specific scripts/makefile > > snippets. > > Well, that's what Robert is pushing. But IMO we shouldn't try to > reinvent THAT wheel (the package building/packing functionality that > other all-in-one package management solutions provide). In other words, > setup.exe shouldn't become the rpm.exe of cygwin, complete with 'setup > -ba myspecfile'. Bleagh. We needn't write another tool for this task, > like "cygpack" or something, with yet another grammar to parse and > learn, to drive autobuilds. Agreed. I never wanted us to reinvent the wheel. Rpm/deb file reading support (not the backend stuff at this point) *is* on the cards. I do want maintainers life to be easy :}. > > Also, while I am/was willing to help out the Cygwin project, I'd > > rather work on LilyPond than reinvent packaging/do porting. > > That's fine. Please continue -- scratch your own itch. But folks > shouldn't complain when nobody wants to scratch their itch FOR them, > like provide/maintain rpm. Better words that I could find - ditto from this corner! > > Being only involved occasionally, and going > > through the archives directly, I didn't find out about the apps list > > (and open membership) until recently... Point of order: The mailing list website has listed cygwin-apps as being open for forever and a day. > Yep, packaging and setup DEVELOPMENT happen on cygwin-apps. (setup bug > reports, and "wouldn't it be nice if..." belongs on cygwin@ though) Non-public code bug reports do belong here under the guidelines I posted ~ a week ago. net release bugs goto cygwin@. How to tell the difference? If you grok the code you can post a setup bug here (only half joking) :}. Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/