Image_Graph is a PHP based object oriented graph rendering package. It provides a simple yet powerful API to allow a user/developer create versatile graphs, charts and plots. The current incarnation of Image_Graph is a merger of the former Sourceforge package, GraPHPite, and the 'old' Image_Graph package from PEAR. WWW: http://pear.php.net/package/Image_Graph/
State Changed From-To: open->feedback pkg-plist is not required: it is handled by FILES and devel/pear-PEAR/Makefile.common.
Responsible Changed From-To: freebsd-ports-bugs->thierry Take it.
Le Mer 2 mar 05 à 17:58:24 +0100, Nick Hilliard <nick@foobar.org> écrivait : > > pkg-plist is not required: it is handled by FILES and > > devel/pear-PEAR/Makefile.common. > > Yup, aware of this, thanks. > > I used pkg-plist to create an entry for: > > %%PEARDIR%%/Image/Graph/Fonts/fontmap.txt-dist > > Perhaps it would have been better to have done this in the Makefile > instead: > > PLIST_FILES+= Image/Graph/Fonts/fontmap.txt-dist > > What do you think? It would be easier to add fontmap.txt & fontmap.txt-dist in the list of FILES: they would be installed and registered by the mechanism of devel/pear-PEAR/Makefile.common. You could add a post-patch: target to copy fontmap.txt to fontmap.txt-dist. Remark: the pear installer replaces all "@package_version@" by PORTVERSION; you could use reinplace to do it. Regards, -- Th. Thomas.
> It would be easier to add fontmap.txt & fontmap.txt-dist in the list of > FILES: they would be installed and registered by the mechanism of > devel/pear-PEAR/Makefile.common. You could add a post-patch: target to > copy fontmap.txt to fontmap.txt-dist. I've removed pkg-plist and have used PLIST_FILES instead. As you suggest, there's no need for pkg-plist after all. > Remark: the pear installer replaces all "@package_version@" by > PORTVERSION; you could use reinplace to do it. Noted - good point. I've also included DOCS and TESTS. Nick
Le Jeu 3 mar 05 à 17:21:08 +0100, Nick Hilliard <nick@foobar.org> écrivait : > Noted - good point. I've also included DOCS and TESTS. OK, thanks. But there is another point: XCONF is set to "/etc/xorg.conf /etc/XF86Config" but for example on my 4.11 machine, /etc/X11/XF86Config is used. According to "man 5 XF86Config": XFree86 uses a configuration file called XF86Config for its initial setup. This configuration file is searched for in the following places when the server is started as a normal user: /etc/X11/<cmdline> /usr/X11R6/etc/X11/<cmdline> /etc/X11/$XF86CONFIG /usr/X11R6/etc/X11/$XF86CONFIG /etc/X11/XF86Config-4 /etc/X11/XF86Config /etc/XF86Config /usr/X11R6/etc/X11/XF86Config.<hostname> /usr/X11R6/etc/X11/XF86Config-4 /usr/X11R6/etc/X11/XF86Config /usr/X11R6/lib/X11/XF86Config.<hostname> /usr/X11R6/lib/X11/XF86Config-4 /usr/X11R6/lib/X11/XF86Config It would be safer to get the fontpath by another program (perhaps xlsfonts or something like that). Regards, -- Th. Thomas.
Thierry Thomas wrote: > It would be safer to get the fontpath by another program (perhaps > xlsfonts or something like that). I wasn't particularly happy with the XORG stuff. As you pointed out, there are many locations where the X configuration stuff can be found, and that's not really satisfactory from a ports point of view. xlsfonts doesn't provide the path to the font, which is what i'm looking for. Either it should be dumped completely, or else some other program be used. The only suitable command that springs to mind is: locate \*.'[Tt][Tt][Ff]' Nick
Le Ven 4 mar 05 à 2:20:53 +0100, Nick Hilliard <nick@foobar.org> écrivait : > >It would be safer to get the fontpath by another program (perhaps > >xlsfonts or something like that). > > I wasn't particularly happy with the XORG stuff. As you pointed out, > there are many locations where the X configuration stuff can be found, > and that's not really satisfactory from a ports point of view. > > xlsfonts doesn't provide the path to the font, which is what i'm looking > for. Sorry, you're right. There should be another command to report the config file, something like `X -config`, but I could not remember it... > Either it should be dumped completely, or else some other program be > used. The only suitable command that springs to mind is: > > locate \*.'[Tt][Tt][Ff]' This find also files installed by JDKs. So, do we remove it? Regards, -- Th. Thomas.
> This find also files installed by JDKs. > > So, do we remove it? Thierry See attached shar, which has removed the script and replaced it with a static message which suggests running a script which uses locate to find all the ttf's on the system and link them into the Fonts directory. I tried playing around with various options here to print up a message which would automatically display a message containing the correct path. However, /usr/ports/devel/pear-PEAR/Makefile does some really funky stuff, including grabbing the post-install target and using that in combination with its own pkg-install to do the pear installation. This means that local pkg-install files are ignored for pear pkgs. Probably it would be possible to do something really hacky to get around this. But I don't think it's worth it in terms of making the package easy to maintain. Probably the pear installation stuff is going to move into /usr/ports/Mk some day at which point, local pkg-install files will be available for use again. Nick
State Changed From-To: feedback->closed New port added, thanks!