To use the epdspdf (and epdspdftk) scripts provided in texlive-pictures (at least in the 2008 version) requires that: 1) Ruby is installed 2) chmod +x /usr/share/texmf-dist/scritps/epspdf/epspdf.rb Whilst an elog message could be used for the first point, the second point should definitely be done via the ebuild.
(In reply to comment #0) > To use the epdspdf (and epdspdftk) scripts provided in texlive-pictures (at > least in the 2008 version) requires that: Thanks for spotting this > 1) Ruby is installed i've added a rdepend on it > 2) chmod +x /usr/share/texmf-dist/scritps/epspdf/epspdf.rb well... at first the ebuild shouldn't drop the perms to 644; i'm working on a sane way to do that, will be fixed soon
(In reply to comment #1) > > 2) chmod +x /usr/share/texmf-dist/scritps/epspdf/epspdf.rb > > well... at first the ebuild shouldn't drop the perms to 644; i'm working on a > sane way to do that, will be fixed soon should be all good now with the recent changes & revbumps.
Is it really necessary to pull in Ruby for one utility that not everyone is going to use? What does this utility do differently than "epstopdf", which is written in Perl and included in texlive-fontutils (which in turn is pulled in by app-text/texlive)? This dependency should be keyed to the "ruby" and/or "eps" USE flags. The USE flag(s) can be activated by default if you like.
