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 Date: Wed, 3 Dec 2003 17:41:30 +0100 (=?ISO-8859-1?Q?Westeurop=E4ische_Normalzeit?=) From: Ulf-Dietrich Braumann Reply-To: braumann AT izbi DOT uni-leipzig DOT de To: cygwin AT cygwin DOT com Subject: install native/x11 ghostscript Message-ID: Organization: http://www.izbi.de & http://www.informatik.uni-leipzig.de/~ulf X-X-Sender: ulf AT axes DOT informatik DOT uni-leipzig DOT de MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at v1-ul Hello, starting to use the newly available gv, I noticed the following conflict between the native and x11 ghostcript packages: Using the cygwin setup, even if I try to selectively install just ghostscript-x11 (besides ghostscript-base, of course), next time I run the setup, without manual intervention the ghostscript native will be installed, too, which in fact should not be necessary. However, if I let happen this, gv will complain about the missing x11 or x11alpha devices, because in my search path, /bin/gs.exe will be found before /usr/X11R6/bin/gs.exe, maybe since X11 was initially not installed. To circumvent further conflicts I simply put a copy of the X11-capable gs into /bin just overwriting the native gs already residing there. My question simply is, why setup recommends installing the native gs even if the x11 version was already installed, or even further, if there is some mechanism to ensure exclusive installation of such packages. Greetings and thanks Ulf-Dietrich -- 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/