Dominik 'Rathann' Mierzejewski wrote:
Do you mean foo2* packages from RPMFusion? :)
I mean a drop-in replacement for the hplip-plugin based on the foo2* code,
or even just on jbigkit, depending on how the hplip code is structured.
Kevin Kofler
--
devel mailing list
On Thursday, 17 March 2011 at 07:48, Kevin Kofler wrote:
Dominik 'Rathann' Mierzejewski wrote:
Do you mean foo2* packages from RPMFusion? :)
I mean a drop-in replacement for the hplip-plugin based on the foo2* code,
or even just on jbigkit, depending on how the hplip code is structured.
On Wednesday, 16 March 2011 at 06:44, Kevin Kofler wrote:
Tim Waugh wrote:
HP won't open-source them unfortunately.
I think the issue is that the code uses the patented JBIG algorithm.
Let's hope it's the only issue.
Maybe things will change soon when the last JBIG patent expires. If HP
On Sun, 2011-03-13 at 01:14 +0100, Dominik 'Rathann' Mierzejewski wrote:
For Tim: have you considered doing something similar to RPMFusion akmod,
i.e. modifying hp-setup/hp-plugin to build an appropriate package
on-the-fly? Also, the binary plugins get installed under /usr/share/hplip,
which
Tim Waugh wrote:
HP won't open-source them unfortunately.
I think the issue is that the code uses the patented JBIG algorithm.
Maybe things will change soon when the last JBIG patent expires. If HP still
doesn't want to free the plugin code then, we could at least ship a Free
replacement if
Hello Tim et al.
Recently, I found out that certain HP devices require binary-only firmware
and plugins. Apparently, this is done via hp-setup, which runs hp-plugin
to download the actual files from www.openprinting.org and copies them
into selected directories under /usr/share/hplip (and puts
