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 To: "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> Organization: Jan at Appel From: Jan Nieuwenhuizen Date: 03 Dec 2001 15:02:17 +0100 In-Reply-To: <9517228633.20011203135833@familiehaase.de> ("Gerrit P. Haase"'s message of "Mon, 3 Dec 2001 13:58:33 +0100") Message-ID: Lines: 29 User-Agent: Gnus/5.090003 (Oort Gnus v0.03) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii "Gerrit P. Haase" writes: > Nah, what I meant, there is a function in libpng not found because tetex > was linked against another version and the table layout changed (unfortunately), > so tetex needs a rebuild with the current libpng. Yes, I've asked Jerome for a rebuild (after trying myself; I gave up). > I may missed some important point, be sure to lookup > http://cygwin.com/setup.html Thanks. I know about that page; but I'm not sure about the status of all individual items; notably the absolute silly reversed-patch requirement. I've seen some discussion, but no conclusion or agreement... I've tried to stay within the spirit of it, the packages should now be mostly complient. (Fwiw, I think it's totally silly to reinvent package management for the umpteenth time. Three years ago, I ported RPM and (cross-)built all my Cygwin (lilypond-support) packages as RPMS. RPM didn't catch on, and I built a set of cross-build scripts from the .spec shell-snippets. But now discussions on cygwin-apps mention 'RPM-like' behaviour and layout. Sigh.) Jan. -- Jan Nieuwenhuizen | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org -- 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/