After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 84166 - pango-querymodules doesn't respect DESTDIR
pango-querymodules doesn't respect DESTDIR
Status: RESOLVED DUPLICATE of bug 129534
Product: pango
Classification: Platform
Component: general
1.0.x
Other Linux
: Normal minor
: future
Assigned To: pango-maint
pango-maint
Depends on:
Blocks:
 
 
Reported: 2002-06-04 20:00 UTC by Sven Neumann
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sven Neumann 2002-06-04 20:00:42 UTC 
In the modules directory, the install-data-local hook calls
pango-querymodules to generate a pango.modules file. It does installs the
generated file correctly in DESTDIR but it should also parse the modules
installed in DESTDIR and remove the DESTDIR part from the generated file.

I guess the cleanest way to fix this is to hack pango-querymodules so that
it looks for a DESTDIR environment variable or (even better) takes an
optional command-line parameter that allows to specify DESTDIR (for example
--destdir=<DIR>).
Comment 1 Owen Taylor 2002-06-04 20:25:24 UTC 
Note that it's not particularly _useful_ to support DESTDIR
in this context; if you are packaging pango, 
pango-querymodules should be rerun at package installation
time.
Comment 2 Abel Cheung 2003-06-23 09:16:32 UTC 
So this bug can be considered as packaging issue, and the report can
be closed?
Comment 3 Owen Taylor 2003-06-23 10:04:02 UTC 
Well, it might be nice to fix for the sake of elegance, or if
someone is using DESTDIR for something other than package
creation.
Comment 4 Owen Taylor 2004-12-13 20:35:40 UTC 
Example Carl Worth mentioned to me recently was "stow" -
http://www.gnu.org/software/stow/ - though that has some compat problems
with libtool's handling of DESTDIR as well.

But actually, this gets fixed by the rewrite of pango.modules handling
planned for bug 129534.

*** This bug has been marked as a duplicate of 129534 ***