public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Markus Hoenicka <Markus.Hoenicka@uth.tmc.edu>
Cc: cygwin@cygwin.com
Subject: Re: tetex-beta nitpicking [WAS: Re: no more package moratorium?]
Date: Sun, 11 Nov 2001 08:26:00 -0000	[thread overview]
Message-ID: <m3n11n3add.fsf@appel.lilypond.org> (raw)
In-Reply-To: <15348.5126.44000.631380@gargle.gargle.HOWL> (Markus Hoenicka's message of "Thu, 15 Nov 2001 19:14:14 +0000")

Markus Hoenicka <Markus.Hoenicka@uth.tmc.edu> writes:

> Did you install the teTeX texmf tree? Just installing Tetex-beta is
> not enough, as explained by the Tetex-beta readme.

This is exacly why I asked if there was any chance if this would get
fixed (.. is not enough), or if tetex-beta would be removed or marked
experimental again with this lifted package moratorium new strictness.

It would be Very Good (TM), if installing a package (and its
dependencies, eg, tetex-texmf) would be `enough' for the package to
work.  This is what Debian and Red Hat packages do, usually.

Having a broken package that doesn't get fixed by it's maintainer is
arguably worse than having none at all.  Maybe Cygwin should introduce
something like Debian's Non-maintainer uploads to address this problem?

Greetings,
Jan.

-- 
Jan Nieuwenhuizen <janneke@gnu.org> | 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/

  parent reply	other threads:[~2001-11-15 23:03 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-02 12:06 no more package moratorium? Gareth Pearce
2001-11-02 12:19 ` Robert Collins
2001-11-11  8:26   ` Robert Collins
2001-11-11  8:26   ` Corinna Vinschen
2001-11-11  8:26     ` Jan Nieuwenhuizen
2001-11-11  8:26       ` Markus Hoenicka
2001-11-11  8:26         ` Stipe Tolj
2001-11-11  8:26           ` Charles Wilson
2001-11-11  8:26             ` Christopher Faylor
2001-11-11  8:26       ` Stipe Tolj
2001-11-11  8:26         ` Robert Collins
2001-11-11  8:26           ` Stipe Tolj
2001-11-11  8:26             ` Robert Collins
2001-11-11  8:26               ` Stipe Tolj
2001-11-11  8:26                 ` Robert Collins
2001-11-11  8:26                   ` Christopher Faylor
2001-11-11  8:26                   ` Stipe Tolj
     [not found]       ` <m3k7wr50fa.fsf@appel.lilypond.org>
2001-11-11  8:26         ` tetex-beta nitpicking [WAS: Re: no more package moratorium?] Markus Hoenicka
2001-11-11  8:26           ` Charles Wilson
2001-11-11  8:26             ` Markus Hoenicka
2001-11-11  8:26           ` Jan Nieuwenhuizen [this message]
2001-11-11  8:26             ` Robert Collins
2001-11-11  8:26           ` Jan Nieuwenhuizen
2001-11-11  8:26             ` Charles Wilson
2001-11-11  8:26               ` Jan Nieuwenhuizen
2001-11-11  8:26             ` Markus Hoenicka
2001-11-11  8:26               ` Robert Collins
2001-11-11  8:26                 ` Markus Hoenicka
2001-11-11  8:26                   ` Jerome BENOIT
2001-11-11  8:26                     ` Robert Collins
2001-11-11  8:26     ` no more package moratorium? Robert Collins
2001-11-11  8:26       ` Christopher Faylor
2001-11-11  8:26         ` Robert Collins
2001-11-11  8:26         ` Jesper Eskilson
2001-11-11  8:26           ` Christopher Faylor
2001-11-11  8:26             ` Stipe Tolj
2001-11-11  8:26         ` Stipe Tolj
2001-11-11  8:26       ` Stipe Tolj
2001-11-11  8:26       ` Robert Collins
2001-11-11  8:26 ` Gareth Pearce
2001-11-11  8:26 tetex-beta nitpicking [WAS: Re: no more package moratorium?] Robinow, David
2001-11-11  8:26 Gary R Van Sickle
2001-11-11  8:26 ` Robert Collins
2001-11-11  8:26 Gary R Van Sickle
2001-11-11  8:26 ` Markus Hoenicka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3n11n3add.fsf@appel.lilypond.org \
    --to=janneke@gnu.org \
    --cc=Markus.Hoenicka@uth.tmc.edu \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).