Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3C0F99CF.3010309@ece.gatech.edu> Date: Thu, 06 Dec 2001 11:16:15 -0500 From: Charles Wilson User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20010914 X-Accept-Language: en-us MIME-Version: 1.0 To: Jan Nieuwenhuizen CC: Robert Collins , "Gerrit P. Haase" Subject: Re: experimental texmf packages References: <878764062 DOT 20011128173421 AT nyckelpiga DOT de> <4434079433 DOT 20011129221637 AT familiehaase DOT de> <9517228633 DOT 20011203135833 AT familiehaase DOT de> <3C0D8535 DOT D67735D1 AT ece DOT gatech DOT edu> <00d501c17d93$1936c990$0200a8c0 AT lifelesswks> <3C0E5FE5 DOT 9040908 AT ece DOT gatech DOT edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-milter (http://amavis.org/) Jan Nieuwenhuizen wrote: > Charles Wilson writes: > > >>>different naming convention, ie foo-1.1-cyg.tar.gz? >>> >>probably too late -- non-maintainers who want to build it personally >>should just download and follow the instructions. >> > > Hmm, that sounds awfully unscriptable :-) Am I the only non-maintainer > that uses a script? You're in bsd-ports "make world" mode, I see. I don't think that is a goal, yet. *OUR* concern is "make cygwin work". Cross environments are nice -- but do you really need a cygwin-target man.exe in your cross environment? (no, you don't -- unless you're the man maintainer and are building the man package for official distribution). Cross environments really only need the devel tools, and the libraries. > Now for something constructive. What if I fix my scripts to do the > new convention, and we run that over the archive to rebuild everything? Be my guest...but remember those "corner cases" I mentioned? square peg, round hole? Go back and read the other thread for some of the examples. It is my contention that some (many?) of our ports are not yet ready for autobuilding. (cf. jpeg, ncurses, readline, gettext, ...) It's going to take detailed knowledge of an individual package -- either to turn it into a round peg, or custom-develop a script. Suggestion: pick ONE package. convert it. present it to the maintainer and say "Hey, isn't this cool? Would you like to package up the next official release of XXX this way? I'll help convert your other packages too..." And then move on to the next maintainer's packages... --Chuck -- 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/