Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com To: Charles Wilson Cc: Jan Nieuwenhuizen , Markus Hoenicka , cygwin AT cygwin DOT com Subject: Re: tetex-beta nitpicking [WAS: Re: no more package moratorium?] References: <007f01c16cde$5016de20$0200a8c0 AT lifelesswks> <20011114124323 DOT C24614 AT cygbert DOT vinschen DOT de> <15348 DOT 5126 DOT 44000 DOT 631380 AT gargle DOT gargle DOT HOWL> <3BF42062 DOT B7B96C50 AT ece DOT gatech DOT edu> Organization: Jan at Appel From: Jan Nieuwenhuizen Date: 15 Nov 2001 21:15:39 +0100 In-Reply-To: <3BF42062.B7B96C50@ece.gatech.edu> (Charles Wilson's message of "Thu, 15 Nov 2001 15:06:58 -0500") 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 Charles Wilson writes: > Okay, now this sounds like lilypond is using a modified *cygwin* > setup.exe. Yes. There was a moratorium on packages, so to get cygwin's setup.exe to download and install the precompiled lilypond tarball (and guile, and an out-of-the-box-working tex), there was no choice but use a modified version. > Does lilypond distribute it's own version of MiKTeX, using the cygwin > setup.exe to do the installation (of the custom MikTeX, and the lilypond > stuff)? Yes, indeed, that's it. I think there have been attempts to fix tetex-beta, to work right out of the box, but up till now, no-one has successfully done this and contributed it. So, we continue to include miktex... > Geez. I started out trying to clarify the issue, and ended up confusing > myself. :-) 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/