Bugzilla Bug 92941

The new package GNU Ghostscript 8.16 is available.

This is a completely GNU compliant distribution based on GPL Ghostscript 8.15
from  artofcode, LLC. and Artifex Software, Inc.

You can found a new ebuild for the package app-text/gnu-ghostscript attached.

Thanks to incorporate in the portage tree !

Didier Link


Reproducible: Always
Steps to Reproduce:

Created an attachment (id=59133) [details]
new ebuild attached

(In reply to comment #1)
> Created an attachment (id=59133) [edit] [details]
> new ebuild attached
> 

the name for the ebuild : gnu-ghostscript-8.16.ebuild

:)

sorry, we don't support gnu ghostscript, only esp and afpl 
 
esp and gnu will also merge in some time soon 

afpl ghostscript is the original ghostscript variant under the aladin licence, 
this will be released as gnu ghostscript under the gnu licence after one year. 
 
esp and gnu ghostscript are essentially the same, only esp ghostscript has cups 
support by default, so it does not make sense to maintain yet another 
ghostscript variant 

I'm the manager of this project for gnu, that's why i send you a working ebuild
(on x86 at least) for this official release !

I know the history of the project, thanks. Please consider officially my request
to put a really free software in gentoo !!

thanks

Didier LINK

I think the GPL-Ebuild is worth consideration.

-               dodir /usr/share/ghostscript/Resource
-               dodir /usr/share/ghostscript/Resource/Font
-               dodir /usr/share/ghostscript/Resource/CIDFont
-               cd ${D}/usr/share/ghostscript/Resource
+               dodir /usr/share/ghostscript/${PV}/Resource
+               dodir /usr/share/ghostscript/${PV}/Resource/Font
+               dodir /usr/share/ghostscript/${PV}/Resource/CIDFont
+               cd ${D}/usr/share/ghostscript/${PV}/Resource


Why did you change that from the -afpl ebuild?
Any specific reason or just4fun? :)

hm, does not work for me :(

# gs
GNU Ghostscript 8.16: Can't find initialization file gs_init.ps.


Any idea?

The reason is that gnu-ghostscript install his resources in a versionned
directory and that's the reason why they don't work actually ... sorry for that,
shame on me ....

I search where is the mistake in the version number, thanks for point it !

Didier

Found the mistake, it's in the ebuild that fixe the search path with the 8.15
version, bad idea :). I reattach a fixed version.

Thanks !

Didier

Created an attachment (id=59160) [details]
gnu-ghostscript-8.16.ebuild

The good one !

And I fix a mistake in the tarball, I reload it on the ftp site. Please reload
it before testing, thanks.

I redownloaded and tried again, strangely enough it was the same tarball.

But after merging with your new ebuild I got the same bug again :(


Please provide an actually working ebuild(or tarball?) :)

Fixed now I hope :)

Just a little problem I've seen in a sub-package, during the configuration of
the ijs subdirectory I have this error :

[blabla]
checking for correct ltmain.sh version... no

*** Gentoo sanity check failed! ***
*** libtool.m4 and ltmain.sh have a version mismatch! ***
*** (libtool.m4 = 1.5.18, ltmain.sh = 1.5.16) ***

Please run:

  libtoolize --copy --force

if appropriate, please contact the maintainer of this
package (or your distribution) for help.

make: *** [config.status] Erreur 1

!!! ERROR: app-text/gnu-ghostscript-8.16 failed.
!!! Function src_compile, Line 92, Exitcode 2
!!! make failed
!!! If you need support, post the topmost build error, NOT this status message.

What's wrong with libtool ?? If I downgrade to libtool-1.5.16 it's ok ...

Thanks for your patience !

Didier

(In reply to comment #12)
> Fixed now I hope :)

How is it fixed?

Ahm, I think it is better to make a renamed tarball, because I still get the
same MD5 from gnu.org

> 
> What's wrong with libtool ?? If I downgrade to libtool-1.5.16 it's ok ...
> 
Maybe you should run the libtoolize --copy --force with the new libtool
installed before packaging it :)


> Thanks for your patience !

No problem.

> Ahm, I think it is better to make a renamed tarball, because I still get the
> same MD5 from gnu.org

It works for me, You have the same error with gs_init.ps missing ? Have you
updated the ebuild (2005-05-17 16:16 PDT) ?

> 
> > 
> > What's wrong with libtool ?? If I downgrade to libtool-1.5.16 it's ok ...
> > 
> Maybe you should run the libtoolize --copy --force with the new libtool
> installed before packaging it :)

I've done it yesterday and the version of libtool change this morning :( ... For
each changes of libtool version all packages need to be updated ? It's a loss of
time no ?

Thanks

Didier

I just did a bit of reading to try to understand these various ghostscript
versions.  Here is my understanding:
AFPL Ghostscript: non-Free version developed by Aladin.
GPL Ghostscript: source code released under GPL by Aladin but delayed by 1 year
from AFPL.
ESP Ghostscript: various patches to GPL Ghostscript.  Maintained by CUPS
developer ESP.  Currently Gentoo GNU/Linux's default ghostscript distro.
GNU Ghostscript: version maintained by FSF which closely follows the GNU
philosophy.  Lead maintainer is Didier Link, submitter of this bug.

Some confusion is currently possible because GPL Ghostscript used to be called
GNU Ghostscript.

If what I said above is correct, then the description of the
app-text/ghostscript ebuild for ESP Ghostscript should probably say:
"ESP Ghostscript -- an enhanced version of GPL Ghostscript with better printer
support"
that is, s/GNU/SPL/

Colin :

You're right,

Please don't be confused between GPL and GNU :)

Stefan :

The ebuild and the tarball work perfectly on my Gentoo (~86) with libtool-1.5.16
installed. Have you a suggestion about the problem of ltmain.sh ?
Thanks

Didier

Created an attachment (id=59624) [details]
gnu-ghostscript-8.16.ebuild

Finally I add the "libtoolize --copy --force" in the ebuild ... only one
solution without a working libtool.eclass

Tested on amd64, no problems.

Thanks

Didier

Thank you, I will have faster internet to look at it again in a week. 

thank you very much
the ebuild is in portage now, should be available for rsync in one hour.