<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Japanese text not rendered from a pdf" href="https://bugs.freedesktop.org/show_bug.cgi?id=81746#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Japanese text not rendered from a pdf" href="https://bugs.freedesktop.org/show_bug.cgi?id=81746">bug 81746</a> from <a class="email" href="mailto:jehan@zemarmot.net" title="Jehan <jehan@zemarmot.net>"> Jehan</a> <pre>Well, you choose. But pkg-config won't ever break any existing script. pkg-config has ever been just a *plus*, not a replacement. If someone don't care and don't want to use pkg-config, this won't break anything existing currently. On the other hand, if someone would like to check for the package existence, pkg-config is the cleaner and safer existing way. A lot of data packages use pkg-config (checking my /usr/share/pkgconfig, I see: iso codes, GNOME themes, udev, X Keyboard configuration data, Freedesktop common MIME db...). That's just the best current way currently to link a program to a set of independent data which could be anywhere in the system. Also there is another advantage: it will allow also to manage versionning. If you improve your encoding packages, add new ones, or fix existing, right now there is no way for a third party to ensure to have the right versions. With pkg-config, you could add dependencies based on versions. In any case, I repeat: that won't break any existing stuff. That just adds a .pc file in the datadir. If third party don't care, they just don't use it. The existing script will still work. I know that in GIMP, I will care so that the next Windows (or other) builds, the packager would not forget the package.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>