Update of port print/gsfonts. Upgrade to the fonts now included in print/ghostscript-gnu After that is posible to take-off gs fonts from ghostscript and make the ports run depends on print/gsfonts
I noticed after your update, the port no longer installs %{FONTSDIR}/Fontdir file. Will this cause problems? -- Pav Lucistnik <pav@oook.cz> <pav@FreeBSD.org>
El Jueves, 3 de Junio de 2004 23:01, Pav Lucistnik escribi=F3: > I noticed after your update, the port no longer installs > %{FONTSDIR}/Fontdir file. Will this cause problems? All this is about make the ghostscript ports run-depends on this and take off the fonts. (next move). At last here, the final pkg-plist is on the way with the font part of print/ghostscript-gnu, with: =2D copy notice, =2D fonts =2D fonts.dir, fonts.scale for use with X. =2D X supportTested with and without fontconfig/libXFT =2D docs moved to ${LOCALBASE}/share/docs/gsfonts I can't respond of the previous layout. The most agressive change is made with sed to make the port a candidate for replacement of x11-fonts/urwfonts as dependencie of ports like java/jdk14 (Adobe foundries, not URW in fonts.dir). Also tested here without problems (I can now take off the other uwr type1 fontpacks like x11-fonts/urwfonts and the type1 component of x11-fonts/XFree86-4-fontScalable). As a side effect I can be sure now of using the same Adobe(well, URW) type1 fonts with X and gs. =2D- josemi
El Viernes, 4 de Junio de 2004 10:13, Pav Lucistnik escribi=C3=B3: > V p=C3=A1, 04. 06. 2004 v 10:07, Jose M Rodriguez p=C3=AD=C5=A1e: > > > > > I noticed after your update, the port no longer installs > > > > > %{FONTSDIR}/Fontdir file. Will this cause problems? > > > > > > Ok I see, but you haven't responded to my original question - > > > after your update it no longer installs ${FONTSDIR}/Fontdir file, > > > and there are two other ports that depend on this file. Will this > > > change break them? > > > > > > editors/ted > > > korean/hlatexfonts-ocf > > > > Pretty sure. But I recall that the original port doesn't work for > > me. > > > > I'll take a closer look on this, at last, on ted (my hangul is > > somewhat baddly broken). > > > > But I gess that the problem may be solved taking a better file to > > depend on (Eg., COPYING). > > > > The fonts.* files aren't good replacement candidates. They may > > disappear in the future with the use of libXFT, while COPYING is > > required by the distribution license. > > We can just depend on one of font files, that's not the problem. > My concern is rather if those ports need the Fontdir file itself. > I don't have any onhand experience with them, myself. If you assume > me they will work after gsfonts update, I will commit your PR. Digging on this, I'm wrong about de gsfonts port. It built OK now. The dependencie of korean/hlatexfonts-ocf is on Fontmap, not Fontdir. I think that recent versions of gs don't use this file any more. Both gnu and afpl gs use an equivalent file under lib (Fontmap or =46ontmap.GS). The file is not part of the fontpack, is generated by type1inst. I really want make the port not builddepend of X. Even, this port colides with any version of gs (Install the same fonts on the same directory). I'm think that the way to go is tweak korean/hlatexfonts-ocf to use gs, not gsfonts. But it isn't a trivial task. I can also run type1inst as before, but see my objections. An other option may be tweak de lib/Fontmap file of gs and make the work of hlatexfonts-ocf with Fontmap not happend (Best way). This may be of interest for other language/country needs. Comments on this are welcome. I'm CCing this to the hlatexfonts-ocf maintainer and wait for further comments. Going for ted. =2D- josemi
State Changed From-To: open->closed Committed, thanks!
Hi; At first I thought this was a good idea, but looking at the commit, I have to object. The fonts in the port (that come with GNU ghostscript) were replaced by those used by AFPL ghostscript. Both versions, and their associated fonts have different license and according to the AFPL license we are not allowed to distribute them on the CD distribution. " ... the AFPL license, unlike the GNU license, prohibits all commercial distribution (unless you get a commercial license from Artifex Software Inc., which is currently the only entity authorized by artofcode LLC to grant such licenses.)" This also means the update done on the GNU ghostcript port some time ago is wrong. The fontconfig stuff (replacing the p5 script) is probably OK and the old URLs should be updated too though.. cheers, Pedro. Yahoo! Mail - Votre e-mail personnel et gratuit qui vous suit partout ! Créez votre adresse sur http://mail.yahoo.fr
V so, 05. 06. 2004 v 02:30, Pedro F. Giffuni pí¹e: > Hi; > At first I thought this was a good idea, but looking at the commit, I have to > object. The fonts in the port (that come with GNU ghostscript) were replaced by > those used by AFPL ghostscript. Both versions, and their associated fonts have > different license and according to the AFPL license we are not allowed to > distribute them on the CD distribution. Well, the file COPYING included in the tarball ghostscript-fonts-std-8.11.tar.gz is a copy of GPL. -- Pav Lucistnik <pav@oook.cz> <pav@FreeBSD.org> Oh, no! Aaargh! It is the most unnatural, most disgusting creature imaginable: a two-eyed cyclops!
--- Pav Lucistnik <pav@FreeBSD.org> a écrit : > V so, 05. 06. 2004 v 02:30, Pedro F. Giffuni pí¹e: .... > Well, the file COPYING included in the tarball > ghostscript-fonts-std-8.11.tar.gz is a copy of GPL. > Hmm.. things have definitely changed (for good)! I tried to convince Peter L. Deutsh (I think that's his name ..it was long ago) to LGPL them as they claimed GPLing them would not be acceptable for Aladdin's distribution. I guess it's Artiflex's problem now ;) . Sorry for getting the facts wrong, keep up the good work! Pedro. Yahoo! Mail : votre e-mail personnel et gratuit qui vous suit partout ! Créez votre Yahoo! Mail sur http://fr.benefits.yahoo.com/ Dialoguez en direct avec vos amis grâce à Yahoo! Messenger !Téléchargez Yahoo! Messenger sur http://fr.messenger.yahoo.com