[UPDATE] print/hplip + RUN_DEP of py-gobject
Hi,
I've found installing the OpenPrinting HPLIP plugins
with their python script needs py-gobject installed.
FreshPorts shows devel/py-gobject as both build & runtime dependencies:
http://www.freshports.org/print/hplip/
I'm not sure if it would be better in some other port, such as py-dbus.
Also update the README for mostly non-root plugins fetch/install:
Index: Makefile
===
RCS file: /cvs/ports/print/hplip/Makefile,v
retrieving revision 1.127
diff -u -p -r1.127 Makefile
--- Makefile17 Apr 2015 04:18:13 - 1.127
+++ Makefile6 Jun 2015 07:49:27 -
@@ -10,6 +10,7 @@ COMMENT-hpijs=HP ghostscript driver (s
COMMENT-gui= HPLIP graphical tools
V= 3.15.4
+REVISION= 0
DISTNAME= hplip-${V}
SUBST_VARS=V
@@ -107,6 +108,8 @@ LIB_DEPENDS-hpijs= print/hplip,-common \
# foomatic-rip(1), foomatic-db(-engine)
RUN_DEPENDS-hpijs += print/cups-filters
+
+RUN_DEPENDS-hplip += devel/py-gobject
### -gui
WANTLIB-gui += #empty
Index: pkg/README-common
===
RCS file: /cvs/ports/print/hplip/pkg/README-common,v
retrieving revision 1.6
diff -u -p -r1.6 README-common
--- pkg/README-common 15 Aug 2014 15:45:38 - 1.6
+++ pkg/README-common 6 Jun 2015 07:49:27 -
@@ -103,8 +103,10 @@ Plugin installation
Some devices will not work properly without a corresponding proprietary
binary plugin. HPLIP plugins automated installation is not available on
OpenBSD but it can be installed manually by running the following as
-root:
-cd /tmp
+non-root:
+cd $(mktemp -d)
ftp
http://www.openprinting.org/download/printdriver/auxfiles/HP/plugins/hplip-${V}-plugin.run
-/bin/sh ./hplip-${V}-plugin.run --keep 2>/dev/null
-cd plugin_tmp && ${MODPY_BIN} ./plugin_install.py -i
+umask 022
+/bin/sh ./hplip-${V}-plugin.run --keep --nox11 --noexec
+cd plugin_tmp && sudo ${MODPY_BIN} ./plugin_install.py -g -i
+
Re: [UPDATE] print/hplip + RUN_DEP of py-gobject
On 2015-06-06 Sat 09:46 AM |, Craig Skinner wrote: > Hi, > > I've found installing the OpenPrinting HPLIP plugins > with their python script needs py-gobject installed. > So as to not clutter the last mail, here's steps to show the dep: $ cd $(mktemp -d) $ umask 022 $ sudo pkg_delete py-gobject $ sudo /etc/rc.d/dbus_daemon restart $ sudo /etc/rc.d/avahi_daemon restart $ sudo /etc/rc.d/cupsd restart $ ftp http://www.openprinting.org/download/printdriver/auxfiles/HP/plugins/hplip-3.15.4-plugin.run $ sh hplip-3.15.4-plugin.run --keep --nox11 --noexec $ cd plugin_tmp/ $ patch plugin_install.py /tmp/plugin_install.py.patch # attached here $ python ./plugin_install.py -g -i ... .. error: Unable to load pkit...is HPLIP installed? error: No module named gobject 162c162 < except ImportError: --- > except ImportError, e: 163a164 > log.error(e)
tcl and tk distinfo
Hi, is it possible that the distinfo files for tcl8.5.18 and tk8.5.18 are wrong? I've problems getting the source files and when I searched online for checksums and checked it manually it seems my downloaded files are good. Regards
Re: tcl and tk distinfo
On Sat, Jun 06, 2015 at 01:31:10PM +0200, Guenther Niess wrote: > Hi, > is it possible that the distinfo files for tcl8.5.18 and tk8.5.18 are > wrong? I've problems getting the source files and when I searched online > for checksums and checked it manually it seems my downloaded files are good. They are wrong. I pinged maintainer this morning. -- Antoine
Re: [update] graphics/p5-Image-ExifTool
ping? :-)
On 4/6/15, patrick keshishian wrote:
> On 4/6/15, Andrew Fresh wrote:
>> On Mon, Apr 06, 2015 at 01:58:11PM -0700, patrick keshishian wrote:
>>> Image-ExifTool-9.76 -> 9.90
>>
>> This looks ok to me, so many new cameras supported! It looks nifty, I
>> may have to try it for something.
>
> Yes, very useful tool. Back in the day, when I used to do
> high-volume photography, it made it very simple to write
> a script for archiving/organizing images off of CF/SD cards
> onto HDD by camera make and image date, for example.
>
> Cheers,
> --patrick
>
>> https://metacpan.org/changes/distribution/Image-ExifTool
>>
>>>
>>> lightly tested.
>>>
>>> Cheers,
>>> --patrick
>>
>>> Index: Makefile
>>> ===
>>> RCS file: /cvs/obsd/ports/graphics/p5-Image-ExifTool/Makefile,v
>>> retrieving revision 1.34
>>> diff -u -p -u -p -r1.34 Makefile
>>> --- Makefile24 Nov 2014 09:32:45 - 1.34
>>> +++ Makefile6 Apr 2015 20:54:07 -
>>> @@ -2,7 +2,7 @@
>>>
>>> COMMENT= read and write meta information in image/audio/video files
>>>
>>> -DISTNAME= Image-ExifTool-9.76
>>> +DISTNAME= Image-ExifTool-9.90
>>> CATEGORIES=graphics
>>>
>>> HOMEPAGE= http://owl.phy.queensu.ca/~phil/exiftool/
>>> Index: distinfo
>>> ===
>>> RCS file: /cvs/obsd/ports/graphics/p5-Image-ExifTool/distinfo,v
>>> retrieving revision 1.28
>>> diff -u -p -u -p -r1.28 distinfo
>>> --- distinfo24 Nov 2014 09:32:45 - 1.28
>>> +++ distinfo6 Apr 2015 20:54:07 -
>>> @@ -1,2 +1,2 @@
>>> -SHA256 (Image-ExifTool-9.76.tar.gz) =
>>> T7GlPNvWlZ5p7DjnvVwth9swlcj4YibTy2fcUNp8BCA=
>>> -SIZE (Image-ExifTool-9.76.tar.gz) = 3892850
>>> +SHA256 (Image-ExifTool-9.90.tar.gz) =
>>> ZPYCdzzSBR/Tq2FEZPSzlJI4O6J0ImPN27TfJ4VbcIk=
>>> +SIZE (Image-ExifTool-9.90.tar.gz) = 3940771
>>> Index: pkg/PLIST
>>> ===
>>> RCS file: /cvs/obsd/ports/graphics/p5-Image-ExifTool/pkg/PLIST,v
>>> retrieving revision 1.23
>>> diff -u -p -u -p -r1.23 PLIST
>>> --- pkg/PLIST 10 Oct 2014 07:31:45 - 1.23
>>> +++ pkg/PLIST 6 Apr 2015 20:54:07 -
>>> @@ -120,6 +120,7 @@ ${P5SITE}/Image/ExifTool/MIE.pm
>>> ${P5SITE}/Image/ExifTool/MIEUnits.pod
>>> ${P5SITE}/Image/ExifTool/MIFF.pm
>>> ${P5SITE}/Image/ExifTool/MNG.pm
>>> +${P5SITE}/Image/ExifTool/MOI.pm
>>> ${P5SITE}/Image/ExifTool/MPC.pm
>>> ${P5SITE}/Image/ExifTool/MPEG.pm
>>> ${P5SITE}/Image/ExifTool/MPF.pm
>>> @@ -282,6 +283,7 @@ ${P5SITE}/Image/ExifTool/iWork.pm
>>> @man man/man3p/Image::ExifTool::MIEUnits.3p
>>> @man man/man3p/Image::ExifTool::MIFF.3p
>>> @man man/man3p/Image::ExifTool::MNG.3p
>>> +@man man/man3p/Image::ExifTool::MOI.3p
>>> @man man/man3p/Image::ExifTool::MPC.3p
>>> @man man/man3p/Image::ExifTool::MPEG.3p
>>> @man man/man3p/Image::ExifTool::MPF.3p
>>
>>
>> --
>> andrew - http://afresh1.com
>>
>> At the source of every error which is blamed on the computer, you
>> will find at least two human errors, including the error of blaming
>> it on the computer.
>>
>
