From: Brian Dessent <brian@dessent.net>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] libXft/libXft2/libXft-devel-2.1.7: A client-side font API for X applications
Date: Wed, 09 Apr 2008 02:05:00 -0000 [thread overview]
Message-ID: <47FC2439.540BB2D7@dessent.net> (raw)
In-Reply-To: <7zabkbs25d.fsf@vzell-de.de.oracle.com>
"Dr. Volker Zell" wrote:
> This package likes to install the header files to
>
> /usr/include/X11/Xft/*.h
>
> xorg-x11-devel installs a symlink
>
> /usr/include/X11 -> ../X11R6/include/X11
>
> Given that the X11 hierarchy is deprecated, I like to remove this
> symlink in a preremove script.
>
> -------------------- preremove ------------------
> #!/bin/bash
>
> if [ -L /usr/include/X11 ] ; then
> rm -f /usr/include/X11
> fi
> -------------------- preremove ------------------
As Angelo tried to report on the wrong mailing list, this is totally
broken. How are you supposed to compile any X11 apps after installing
this package, without manually adding -I/usr/X11R6/include/X11 to
CPPFLAGS? Simply installing libXft-devel causes all the X11 headers to
no longer work, because the only thing left under /usr/include/X11 is
now Xft/.
It doesn't make any sense to try to deprecate the X11R6 tree until we
actually have working xorg-* packages that use the new layout. libXft
should not and does not "own" /usr/include/X11, so it's very surprising
that installing an ancillary library causes a bunch of headers to move.
xorg-x11-devel should "own" that directory and when we get an X11
maintainer that package should be responsible for moving it out of the
X11R6 space, but not until then, and not by a random library.
Brian
next prev parent reply other threads:[~2008-04-09 2:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 9:46 Dr. Volker Zell
2008-04-06 11:22 ` Corinna Vinschen
2008-04-09 2:05 ` Brian Dessent [this message]
2008-04-09 2:10 ` Brian Dessent
2008-04-10 9:37 ` Dr. Volker Zell
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=47FC2439.540BB2D7@dessent.net \
--to=brian@dessent.net \
--cc=cygwin-apps@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).