| | <<<Back 1 day (to 2017/08/16) | 20170817 |
| Flo__ | hey folks, coming here for sort of "bug report" or actually need of help with GS / GSview. | 10:10.37 |
| kens | You can always report bugs to our bug tracker | 10:10.52 |
| | Whether we cna help or not with GSView depends on the versio0n | 10:11.02 |
| Flo__ | yeah I'm not really sure it's a bug | 10:11.14 |
| | so the thing is the file works fine in GS but not in GSview (6.0) | 10:11.46 |
| kens | Hmmm | 10:11.53 |
| Flo__ | it just says "GS can't distill PS". But with "plain" GS i can view the file just fine | 10:12.26 |
| kens | Artifex GSView (gsview 6) isn't the same beast as gsview 5 | 10:12.28 |
| | Flo__ : viewing and 'creating a PDF file' are not teh same thing | 10:12.48 |
| Flo__ | yea I was used to the <5 versions of GSview and now this is a new machine. I was unaware of what is going on behind the scences | 10:13.02 |
| kens | Behind the scenes PostScript is converted to PDF, and then the PDF is opened and siplayed using MuPDF | 10:13.22 |
| | displayed* | 10:13.30 |
| Flo__ | I'm not rally trying to create a PDF, it's just the one error msg that pops up when opening the .ps file with GSview 6.0 | 10:13.36 |
| kens | SO PostScript files have to be turned into PDF | 10:13.43 |
| Flo__ | and GS doesn't do that, I get it. | 10:13.55 |
| kens | GS *does* do that | 10:14.03 |
| | Its why GSView 6 uses it | 10:14.09 |
| | But.... | 10:14.12 |
| Flo__ | no I mean the old GSview versions don't do that | 10:14.24 |
| kens | rendering a PostScript file to bitmap, and creating a PDF file from it, are not the same thing at all | 10:14.28 |
| | Ah right the Ghostgum version didn't do that, no | 10:14.45 |
| | Note that IIRC Artifex GSView doesn't have a replacable Ghostscript | 10:15.02 |
| | So you are using whatever version of Ghostscript was around when it was built (some time back) | 10:15.22 |
| Flo__ | so if i want to use the gs 9.21 (current?) version of ghostscript, which viewer is recommended? | 10:15.28 |
| kens | Well I'd use Ghostscript personally :-) | 10:15.40 |
| | The default device for Ghostscript on Windows is the display device, which will create a Window and render the file to it | 10:16.25 |
| Flo__ | haha, ok maybe worth getting used to, I've only been using the GSview frontend for quite a while and the ghostscript front doesn't look inviting at all ;) | 10:16.52 |
| kens | Actually you probably can replace the Ghostscript in Artifex GSView | 10:17.10 |
| Flo__ | I'll just look at the manual and try to figure it out. Thanks for clarification of that. Is it possible to use "older" GSview versions with the current ghostscript? | 10:17.40 |
| kens | Wherever you installed it will be a 'bin' directory, which includes the Ghostscript DLLs. For now, at least, you can just replace those with the current Ghopstscript build I think | 10:17.51 |
| | Flo__ : I try to make sure that new versions of Ghostscript continue to work with old versions of GSView | 10:18.13 |
| | However, as time goes on that's getting harder and harder to do. I believe teh current release still works (I tested it back in March), but I can't guarantee it into the future | 10:18.43 |
| Flo__ | ok, good to hear. So how is the general relationship of Artifex GSView with older GSView versions and ghostscript in general? | 10:19.47 |
| kens | Artifex GSView 'might' work with older versions of Ghostscript, I wouldn't recommend tryin it. | 10:20.19 |
| | But Artifex GSView and Ghostgum GSview are totally different, only the name remains the same | 10:20.39 |
| kens | isn#'t sure if that answers the question | 10:21.29 |
| Flo__ | thanks a lot | 10:22.26 |
| deekej | chrisl: hello Chris, do you have a moment now? :) | 10:54.26 |
| | chrisl: I wanted to discuss details of the git submodules | 10:55.13 |
| chrisl | deekej: here now | 11:19.34 |
| deekej | chrisl: cool :) so, the first question that needs answer I guess is, where would you like the git submodule to be hosted? | 11:21.52 |
| | should it be Artifex repository directly on your infrastructure, or should be it hosted on github? | 11:22.29 |
| | on github it can be a completely independent repository, or it can be a repository belonging to Artifex organization there... | 11:22.57 |
| chrisl | I'd be happy to have it on the Artifex github account - then you can clone it, and stick in pull requests | 11:23.44 |
| deekej | chrisl: good, that's okay with me :) | 11:24.56 |
| | the second thing that I have on my mind is that I have created AppStream metadata files as well | 11:25.23 |
| | https://www.freedesktop.org/wiki/Distributions/AppStream/ | 11:25.29 |
| | I would like them to be included there as well | 11:25.39 |
| | AFAIK, the <release/> tag should be added when creating new release, and that can be automated | 11:26.41 |
| | everything should stay pretty much the same | 11:26.59 |
| chrisl | deekej: Actually, I'm thinking maybe we want this to work the other way round: have the git.ghostscript.com repo as a submodule of the github one. So the github one becomes the canonical source for distros | 11:27.54 |
| deekej | chrisl: I'm not sure I follow - do you want to sync the work to github, or do you want to migrate to github completely? | 11:28.53 |
| chrisl | deekej: We create a repo on github which contains the metadata files you want to add/maintain, and that repo has a submodule which is our http://git.ghostscript.com/?p=urw-core35-fonts repo | 11:30.00 |
| deekej | ah, ok | 11:30.24 |
| | but what would be the file/folder structure in that case? (especially in the created archive/release?) | 11:30.57 |
| | I was thinking of having "urw-core35-fonts" as a top directory | 11:31.15 |
| | where the fontconfig & appstream would be a subfolders of that | 11:31.26 |
| | i.e. not to mix your work on fonts and the metadata files | 11:31.48 |
| chrisl | deekej: something like this: https://pastebin.com/GnBhtpAu | 11:33.47 |
| | Where the "fonts" directory would be the submodule | 11:34.00 |
| kholo | Hi, we try to use alias gs to run ghostscript we get the permission denied error despite the fact that the user executing it is the owner, but when execute it using the full path its working. Please help | 11:34.16 |
| deekej | chrisl: ah, so it would have 3 subfolders, and the top folder could contain only - lets say - COPYING and README files? | 11:34.50 |
| chrisl | kholo: that sounds more like a shell question than a ghostscript one | 11:34.53 |
| deekej | kholo: write me PM here, maybe I can guide you a little | 11:35.31 |
| chrisl | deekej: Yes. It might be feasible to have the font files in the top directory - I don't know enough about submodules to know right now | 11:35.55 |
| | deekej, kholo: if you guys want to discuss the issue here, it's fine - it might be useful if it comes up again | 11:36.28 |
| deekej | kholo: OK, what Linux distro are you using ATM? | 11:37.48 |
| | chrisl: ok, I will find out more about the git submodules on how they work, and I will get back to you :) | 11:40.04 |
| chrisl | deekej: it doesn't look like we can just get the files in the top directory..... | 11:41.54 |
| deekej | chrisl: I think if we would like to keep the files as they are, and add only the subfolders with fontconfig/appstream, then it the fontconfig/appstream would have to be a separate git submodule | 11:43.04 |
| | (actually maybe 2 git submodules, I have to check) | 11:43.17 |
| chrisl | deekej: I was thinking something like this: https://github.com/ArtifexSoftware/urw-core35-fonts | 11:47.39 |
| deekej | kholo: what Linux distribution are you using at the moment? | 11:48.21 |
| | chrisl: yeah, this actually looks quite good | 11:48.41 |
| kholo | Its Rhel 7-1, I am running gs 9.19 | 11:49.18 |
| chrisl | deekej: then we can manage the appstream and fontconfig stuff via github pull requests | 11:49.32 |
| deekej | kholo: if it is RHEL-7.1, that means you are running custom ghostscript build... next question, do you have SELinux enabled? | 11:51.11 |
| | chrisl: yes, and the new font releases of the fonts archive could be utilized completely by the github infrastructure | 11:51.55 |
| | chrisl: so you wouldn't have to create the archives manually anymore | 11:52.10 |
| chrisl | deekej: indeed, yes | 11:52.17 |
| deekej | chrisl: so, I will submit the pull-request to the github repository soon | 12:00.46 |
| chrisl | deekej: cool. Let me know if it proves unwieldy or problematic, and we can rejig stuff | 12:02.20 |
| deekej | chrisl: I'm thinking - it might be good to rename the github repository, though, to "urw-base35-fonts" | 12:02.36 |
| | currently cloning the repository from github would conflict with the git.ghostcript.com repository because of the same names | 12:03.07 |
| | and secondly, previously you have released the archive as "urw-bas35-fonts" | 12:03.29 |
| | github releases are based on the github repository name | 12:03.40 |
| chrisl | Done | 12:04.11 |
| deekej | so now the github release would be named "urw-core35-fonts", which is probably something you don't want :) | 12:04.13 |
| | thanks :) | 12:04.16 |
| chrisl | That was easier than I expected | 12:05.23 |
| deekej | chrisl: here's the first pull-request for fontconfig: https://github.com/ArtifexSoftware/urw-base35-fonts/pull/1 | 12:21.18 |
| chrisl | deekej: Done. (Had to work out how pull requests work!) | 12:24.21 |
| deekej | chrisl: hehe, no problem ;) BTW, in the github settings you can enforce things like no force pushes, mandatory reviews, protected branches, etc. | 12:25.18 |
| | chrisl: I guess I can help you with it if something is unclear | 12:25.47 |
| chrisl | It wasn't a problem, I just hadn't been on this side of it before | 12:26.36 |
| deekej | chrisl: ah, ok :) | 12:26.43 |
| | chrisl: do you have any idea how would you like to tag the master branch for the releases? | 12:27.15 |
| | my suggestion would be to stick what you had before, the date without hyphens | 12:27.32 |
| chrisl | deekej: That's fine by me. Unfortunately, that's really the only way we have to id urw's releases | 12:28.02 |
| deekej | chrisl: yeah, I understand :) | 12:28.43 |
| | chrisl: and here is the AppStream PR: https://github.com/ArtifexSoftware/urw-base35-fonts/pull/2 | 12:36.54 |
| chrisl | Also done | 12:37.48 |
| deekej | chrisl: perfect :) | 12:38.45 |
| | chrisl: so, I think the last thing for now would be try to create a new release via github | 12:40.07 |
| | chrisl: do you expect URW to give you any more changes to fonts before ghostscript-9.22? | 12:40.26 |
| | chrisl: if not, we could try it now I guess | 12:40.50 |
| | chrisl: in that case I would submit a new pull-request, and then we're good to go | 12:41.20 |
| chrisl | deekej: No, I don't expect any more from URW. We do have an open issue, but I can't actually see any problems to pass on to URW, so..... | 12:41.43 |
| | I'd like to keep the font release tied to the gs releases. | 12:42.15 |
| deekej | chrisl: so, based on the last commit in urw-core35-fonts, the "version" for the new urw-base45-fonts releases would be "20170801", right? | 12:46.56 |
| | can I submit a pull-request with that version? | 12:47.22 |
| chrisl | Yes, that would be the version. Can you do it as "20170801_test"? So we keep the "20170801" tag for a release coinciding with the next Ghostscript release | 12:49.16 |
| deekej | ah, I think we misunderstood each other :) | 12:49.57 |
| | I want this version to be used in AppStream files, not as the git tag itself ;) | 12:50.20 |
| | give me few minutes, you will see it in the pull-request | 12:50.32 |
| chrisl | Oh, sure, that's fine. | 12:50.33 |
| | Then I'll create a "pre-release" from that | 12:50.46 |
| deekej | chrisl: here are the changes I was talking about: https://github.com/ArtifexSoftware/urw-base35-fonts/pull/3/files | 13:15.30 |
| | in the future I would like to create some way to automate this, to avoid doing pull-request for this before each release :) | 13:16.35 |
| chrisl | deekej: TBH, I'm very much hoping releases will not be often enough to warrant much automation! | 13:17.28 |
| deekej | chrisl: I hope as well :D but I was thinking of creating a small python script, so the Linux distros would run make when creating the font package for their distros | 13:23.17 |
| | this python script would automatically create all the appstream/fontconfig files properly | 13:23.34 |
| chrisl | deekej: Well, this is going to need a rethink - github releases don't include submodules from the repo :-( | 13:24.30 |
| deekej | hmm, really? | 13:24.40 |
| chrisl | Yep | 13:24.59 |
| deekej | yesterday I have found an article about this topic | 13:25.07 |
| | I will find it in the history | 13:25.11 |
| kens | submodules are weird | 13:25.13 |
| chrisl | I was hoping they'd been somewhat unweirded recently | 13:25.43 |
| deekej | I'm currently looking into this: | 13:27.28 |
| | https://ttboj.wordpress.com/2015/07/23/git-archive-with-submodules-and-tar-magic/ | 13:27.28 |
| | in the worst case scenario, we could create a Makefile that would do this | 13:27.57 |
| chrisl | I have to say, this just seems like submodules are broken. I need to give this some thought | 13:30.06 |
| deekej | I'm currently playing with it myself, I will let you know when I know more :) | 13:37.41 |
| | okay, so according to SO, this is not possible on github: | 13:43.44 |
| | https://stackoverflow.com/questions/34719785/how-to-add-submodule-files-to-a-github-release | 13:43.45 |
| | so I will try to create a Makefile which would do all of this automatically and spit up an archive for you | 13:45.07 |
| | that archive would need to uploaded to either github, or ghostscript download page | 13:45.36 |
| chrisl | deekej: TBH, I'm seriously thinking we might be as well just to make github the canonical URW fonts repo, and forget the submoduling | 13:52.20 |
| deekej | chrisl: huh, ok | 14:09.31 |
| | chrisl: I guess that would solve the problem | 14:09.43 |
| chrisl | deekej: Well, what do you think? It just seems too much hassle using the submodule | 14:10.21 |
| deekej | chrisl: If you are OK with moving to github, then I think it's the best solution at the moment | 14:10.58 |
| chrisl | deekej: okay, let's do that. I'll sort it out tomorrow, when I'm less annoyed! | 14:11.40 |
| deekej | chrisl: no problem :) | 14:13.20 |
| | chrisl: btw: you can throw away the changes in the current github repo (urw-base35-fonts) | 14:13.52 |
| | chrisl: and I can sumbit the pull-requests again, to avoid complications | 14:14.07 |
| | chrisl: that should make it easier I guess :) | 14:14.22 |
| chrisl | deekej: I'll try to preserve them - I'll let you know | 14:14.42 |
| deekej | chrisl: ok | 14:14.58 |
| chrisl | deekej: I had to do a forced update, but it all seems to be there intact | 14:30.12 |
| deekej | chrisl: no problem :) | 14:47.05 |
| chrisl | deekej: There's a test release there, which looks okay me | 14:47.43 |
| | Forward 1 day (to 2017/08/18)>>> | |
Log of #ghostscript at irc.freenode.net.