| | <<<Back 1 day (to 2018/02/27) | 20180228 |
| deekej | chrisl: Hello! :) Would you be OK with having a pkg-config file for Ghostscript? | 12:07.05 |
| | chrisl: I could create one. IMHO it could make life (packaging) easier for some other software depending on Ghostscript, like ImageMagick e.g. | 12:09.15 |
| | You already have a pkg-config file in the ijs/ folder | 12:09.31 |
| chrisl | deekej: we've always said no because of the hassle in keeping it up to date | 13:29.09 |
| deekej | chrisl: okay, thanks :) | 13:29.36 |
| chrisl | deekej: the problem is if we include a pkg-config file it will either be incorrect for what we ship, or incorrect for what the distros actually distribute, which makes it a pain | 13:30.30 |
| deekej | chrisl: couldn't be this solved that the pkg-config file would be automatically generated during the build, same as Makefile is? | 13:32.02 |
| | (in other words - to have *.pc.in file, where the paths would be correctly substituted?) | 13:32.49 |
| chrisl | deekej: I hadn't thought of that.... it would be an option, yes | 13:33.00 |
| | It's not so much the paths, but the dependencies | 13:33.26 |
| deekej | this is the way it is done with IJS's pkg-config file | 13:33.27 |
| chrisl | I've barely looked at the IJS builds, tbh | 13:33.50 |
| deekej | I'll check the pkg-config dependencies more | 13:34.01 |
| chrisl | We need to have pkg-config leave out any third party libs that the sources are in the ghostscript source tree | 13:34.47 |
| | But that should be pretty straightforward, I'd think | 13:35.05 |
| deekej | agreed | 13:41.00 |
| | basically, the Ghostscript is able to build itself without 3rd party libs, so when the pkg-config file is used, it should stay that way | 13:41.29 |
| | if any distro do any modifications to the build process, then it's their responsibility to deal with the mess | 13:42.00 |
| chrisl | Every now and then distros use our packaged third party libs (if we have a critical patch that's not available upstream yet), so it would be good if we could make the pkg-config file generation flexible enough to handle that situation | 13:43.39 |
| | Although it is rare | 13:43.43 |
| deekej | hmm | 13:44.06 |
| chrisl | We already have tests in configure.ac for each third party lib | 13:44.36 |
| | deekej: are you going to look at doing this? | 13:51.55 |
| deekej | chrisl: yes | 13:52.03 |
| | I need to understand pkg-config more first, though | 13:52.17 |
| chrisl | Well, if you get something working how you need it, I can massage it to fill in the Ghostscript specialness | 13:53.06 |
| | To be fair (and honest), I'm not that big a fan of pkg-config.... which is probably also a big reason for past refusals | 13:56.11 |
| deekej | I wouldn't think of it either, but I'm currenlty dealing with 2nd bug from ImageMagick, because it has some issues with its own configure script | 13:57.11 |
| | they seem to have some hardwired paths there | 13:57.35 |
| | they suggested the use of pkg-config, so I went with it, if it means less issues in the future | 13:58.08 |
| chrisl | I suspect ImageMagick is in a similar position to Ghostscript - venerable, long standing project, long predating autotools, pkg-config etc, and probably its own baroque build | 13:59.03 |
| deekej | I guess so :) and whenever you fix/enhance something in Ghostscript, it breaks the ImageMagick :) | 14:01.00 |
| chrisl | IIRC, ImageMagick is one of the projects that was using Ghostscript internal-only stuff - so they were skating on ice there | 14:02.23 |
| deekej | AFAICT, they are relying on your API and the libgs library | 14:02.53 |
| chrisl | Well, that API hasn't really changed, as best I can remember | 14:04.11 |
| deekej | yes (currently, some of their tests are failing in Fedora) | 14:05.07 |
| chrisl | I thought they were also using some Ghostscript internal Postscript operators (which we removed a lot of them), but I may be wrong | 14:05.16 |
| deekej | btw: how does the API change look? :) | 14:05.35 |
| kens | distant :-) | 14:05.47 |
| deekej | was it postponed? | 14:05.50 |
| | ah, ok :) | 14:05.52 |
| | I'd like to get it into next major RHEL release, if possible | 14:06.13 |
| chrisl | Which API change? The one I was working on is the device API, which is not the libgs API | 14:06.14 |
| deekej | it would save us a lot of trouble :) | 14:06.19 |
| | chrisl: I don't know exactly, I just recall talking with you guys about some planned API change | 14:06.50 |
| kens | The devoice API change wo't affect any code using the external API | 14:07.19 |
| deekej | basically, any API change is to my concern, to not break anything :) | 14:07.22 |
| kens | It will only affect devices | 14:07.24 |
| | The device API is an internal API | 14:07.42 |
| deekej | ah, ok | 14:07.46 |
| | so let me rephrase my question - are there any external API changes planned? :) | 14:08.26 |
| chrisl | Yes, but very minor | 14:08.54 |
| | So, mostly they'l be extending teh API, and as such, it will remain ABI compatible | 14:10.13 |
| deekej | that pleases me to hear :) | 14:10.30 |
| chrisl | There is one change I'd like to make which might be an ABI change, but I would try to work out a way around that | 14:11.15 |
| | That certainly won't be in the next release. And, frankly, I've no idea if the Ghostscript internals can be reasonably bent to support what I want to do, so I can't make promises | 14:12.53 |
| deekej | so, going back to the pkg-config - I think it should be enough for pkg-config file to provide only the Libs & Cflags (as ijs.pc does) | 14:43.19 |
| | and to set some additional variables for ghostscript's paths that could be accessed via 'pkg-config --variable=NAME' | 14:43.53 |
| chrisl | I'm not sure what paths would be useful for callers to have access to | 14:44.44 |
| deekej | IMHO since by default Ghostscript does not rely on any other 3rd party software, we could omit the Requires | 14:44.48 |
| | those paths would be e.g. path to Resource/ directory, etc. | 14:45.39 |
| chrisl | Yeh, but why would a caller need those? | 14:46.07 |
| deekej | I'm not sure which path exactly the ImageMagick might need | 14:46.07 |
| | I'll ask ImageMagick what paths they actually need and what for | 14:47.10 |
| chrisl | See, it's stuff like the --print-requires that bugs me - we already have configure scripts for that kind of thing..... I'll try not to rant.... | 14:48.41 |
| deekej | I understand - IMHO the Requires: are not necessary for the pkg-config file. | 14:51.31 |
| | at least for Ghostscript | 14:51.44 |
| wallbroken | hi | 20:19.02 |
| ghostbot | Welcome to #ghostscript. If you have a question, please ask it, don't ask to ask it. Do be prepared to wait for a reply as devs will check the logs and reply when they come on line. If you are looking for help or infomation about MuPDF, try the new #mupdf channel. | 20:19.02 |
| wallbroken | anybody? | 20:19.03 |
| | anybody? | 20:39.12 |
| vtorri | tor8 :hey | 20:48.41 |
| | tor8: how can I distinguish mupdf 1.11 and 1.12 at preprocessor time ? | 20:49.03 |
| | Forward 1 day (to 2018/03/01)>>> | |
Log of #ghostscript at irc.freenode.net.