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 Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com Subject: Re: [ANNOUNCEMENT] Updated: tetex-2.0.2-14 References: <200409172057 DOT i8HKv3W01588 AT esds DOT vss DOT fsi DOT com> <87zn3hdmfk DOT fsf AT vzell-de DOT de DOT oracle DOT com> From: Jan Nieuwenhuizen Organization: Jan at Appel Date: Tue, 28 Sep 2004 18:14:52 +0200 In-Reply-To: <87zn3hdmfk.fsf@vzell-de.de.oracle.com> (Volker Zell's message of "Thu, 23 Sep 2004 17:39:27 +0200") Message-ID: <874qli1ibn.fsf@peder.flower> User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by XS4ALL Virus Scanner X-IsSubscribed: yes Note-from-DJ: This may be spam Volker Zell writes: > > tetex-bin (2.0.2-14) > > This package has adopted again the old /usr/doc structure :-( > info > man Oops. My mknetrel addons should automagically have fixed this. I did so many rebuilds that something has gone wrong and apparently I didn't check the last version very carefully. > > tetex-texmf (2.0.2-14) > > You mean tetex-base, right ? Yes, the four packages that are built from the texmf tree. > Shouldn't than this package create the /var/cache/fonts directory > instead of /var/spool/texmf as it is now ? Yes it should. > Although tetex-x11 has some bogus empty dirs: > Ciao > Volker Thanks for your careful inspection. I have prepared a new -15 version that should fix all these problems and then some. I'm about to announce for upload after some more testing this time (lilypond.org/cygwin/). 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 Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/