<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - /opt/bin/make install DESTDIR=/xxx/yyy does not work solely in DESTDIR but also references ${prefix} without ${DESTDIR}" href="https://bugs.freedesktop.org/show_bug.cgi?id=92406#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - /opt/bin/make install DESTDIR=/xxx/yyy does not work solely in DESTDIR but also references ${prefix} without ${DESTDIR}" href="https://bugs.freedesktop.org/show_bug.cgi?id=92406">bug 92406</a> from <a class="email" href="mailto:akira@tagoh.org" title="Akira TAGOH <akira@tagoh.org>"> Akira TAGOH</a> <pre>(In reply to Michael Felt from <a href="show_bug.cgi?id=92406#c2">comment #2</a>) > You can call it "not a bug", but then you may want to document that make > DESTDIR=/something/else will never work because the make process cannot > deal with the symbolic links auto(anything) makes. > Probably "not a bug", at least not of fontconfig - but of one of the > tools you use to automate builds of fontconfig. It looks like you are misunderstanding about DESTDIR. see <a href="https://www.gnu.org/software/automake/manual/html_node/DESTDIR.html">https://www.gnu.org/software/automake/manual/html_node/DESTDIR.html</a> If you want to install them permernently under $DESTDIR, you should do that with --prefix and other options for configure script that determine the install path, instead of using $DESTDIR. I don't know what kind of problems you are facing at this moment though, it works fine with many packaging systems so that I've never ever heard any complaints about it. > IMHO - this is something that auto-thingy should be able to do so that > make DESTDIR=/var/DESTDIR would work. Wrong. you should better understand how packaging systems works to build a package. > (stripping $DESTDIR from the full filepathname That's why symlinks works at the end on packaging system enabled environments. symlinks points to the proper files when installing the package then. Doing both of validating symlinks and creating a package isn't feasible, particularly it contains a symlink. if you are fixing that anyway to work a symlink validation, you'll see a problem after installing that package because symlinks points to $DESTDIR/path/to/file where isn't available. so you eventually need to re-link them. > - but the make command > itself that fails! It's not our fault. no fails with "make" itself on what we shipped.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>