Re: [Gimp-print-devel] Imprimante Epson

[Greg T. <gd...@le...>]

Solomon Peachy <pi...@sh...> writes:

> On Mon, Dec 09, 2019 at 06:37:51PM -0500, Greg Troxel wrote:
>> There is also pkgsrc, which is a multi-OS portable packaging system.  I
>> have been maintaining a gutenprint-lib package, not 100% diligently but
>> often up to date.
>
> Out of curiousity, who/what is using gutenprint-lib?  Having some clue 
> about our downstream users would be hignly beneficial.

Within the pkgsrc context, it can be used as a cups driver and the
gimp-print plugin is also built via pkgsrc.  I have not powered on my
Epson Stylus Photo 2200 (yes, that's over 15 years old) in years, but I
used to use it to print photos.

As to your real question of what the other people that might be using
this in pkgsrc, I have no idea.  We don't have a phone-home tally
system.

>> With pkgsrc, there is no notion of creating official mac dmg installers.
>> There is a foo-1.2.tar.gz "package" which is in pkgsrc format (tarball
>> with the files that go in /opt/pkg and some control files), and one uses
>> pkg_add to add that.  From the point of view of the OS this is just
>> placing programs in the FS.  If even that starts to be restricted, then
>> I don't see a good path forward.
>
> Can files be placed outside of opt for the times when tighter system 
> integration is needed? For example, our CUPS integration needs to be 
> able to shove stuff in the directories for filters, backends, and 
> drivers, with the libraries they need (ie libgutenprint) placed in a 
> place reachable by the global/default LD_LIBRARY_PATH...

pkgsrc has a notion of a configured prefix for all of pkgsrc.  On NetBSD
and other normal unix systems, it's almost always /usr/pkg.   On Mac it
tends to be /opt/pkg because of SIP which doesn't let one write to /usr.

pkgsrc as a rule is allergic to writing files outside its configured
prefix (strictly, there is a PKG_SYSCONFDIR (pkgsrc's private /etc) and
a db dir that records what's installed).   Putting things into the
normal system paths we basically don't do.

I have never tried to integrate the pkgsrc-built gutenprint with the mac
system.  I probably have converted images to epson and then used
lpr/raw, or the gimp-print plugin.

Given what you are saying about system directory integration, pkgsrc
doesn't sound like it solves your issues.  Really the point of pkgsrc is
to have a uniform "build me this", keep track of installs, and be able
to install binary packages.  I think what gutenprint needs is a private
build from source with curated destination paths to overlay the system,
and I'm guessing your current dmg is just that.

So you might consider having a tar.gz that people can unpack and click
"yes really run this".  Which is a dmg without the signature stuff.

>> That seems to be the nature of apple these days.  Not clear if there is
>> a path to thigns going well.
>
> With the envisioned "printing application" future, in many ways the 
> system integration gets easier.  But of course we first need to create 
> said application.  :)