Message-ID: <20051207202800.52568.qmail@web51514.mail.yahoo.com>
Date: Wed, 7 Dec 2005 12:28:00 -0800 (PST)
From: "James R. Phillips" <antiskid56-cygwin AT yahoo DOT com>
Reply-To: antiskid56-cygwin AT yahoo DOT com
Subject: Re: octave-forge dependency?
To: cygwin AT cygwin DOT com
Cc: pechtcha AT cs DOT nyu DOT edu, jwe AT bevo DOT che DOT wisc DOT edu
In-Reply-To: <Pine.GSO.4.63.0512071253390.21598@slinky.cs.nyu.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

--- Igor Pechtchanski wrote:

> Ok, so first off, octave-forge *shouldn't* depend on tetex-bin. If
> anything needs to depend on tetex-bin, it should be gnuplot.  The presence
> of tetex-bin in octave-forge's requires: line is a packaging bug (even if
> it's intended to work around gnuplot's missing dependency).
> 

Igor, if you read the whole thread, you will see that the dependency could not
possibly have been intended to work around a problem with gnuplot, because we
didn't know there was a problem with gnuplot.  All we knew was that there was a
problem with octave-forge.

Now that we know more specifically where the problem is, I can agree that the
tetex-bin dependency for octave-forge causes more problems than it solves, and
should be dropped.

It seems the best solution to this problem lies in updating the gnuplot
package.  In the meantime, users can try the workarounds suggested.

BTW, the gnuplot version in Debian sarge behaves exactly the same way as the
cygwin version in response saving a file if kpsexpand is not present.  And
Debian does not list tetex-bin as a dependency for gnuplot.  Probably this
needs to be researched further with the gnuplot mailing lists.  Possibly some
bugs need to be filed upstream.

--
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/