From: Joshua Kinard <kumba@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Printer drivers and net-print
Date: Fri, 17 Dec 2021 19:37:31 -0500 [thread overview]
Message-ID: <5debb049-dfed-e5ae-f8b1-539fa303f326@gentoo.org> (raw)
In-Reply-To: <20211217195625.a14b68e403db09b744001334@gentoo.org>
On 12/17/2021 11:56, Andrew Savchenko wrote:
> On Fri, 17 Dec 2021 14:00:48 +0100 Andreas Sturmlechner wrote:
>> On Montag, 20. Februar 2017 22:47:17 CET Andreas K. Huettel wrote:
>>> Hey all,
>>>
>>> 1) Putting printer drivers into "net-print" is silly.
>>>
>>> Something that converts format a to device-specific format b has absolutely
>>> nothing to do with network.
>>> So, a new category "sys-print", emphasizing that it's hardware drivers, (or
>>> "cups-drv"?) (or maybe "media-print"?) might make sense.
>>>
>>> 2) After introducing that, however, "net-print" becomes nearly empty.
>>>
>>> On a quick glance, the only *network*-specific packages in there are cups
>>> and lprng. Maybe one or two more which I dont recognize.
>>>
>>> So move cups and lprng to "net-misc" and drop "net-print"?
>>> Or move them to new "sys-print" as well?
>>>
>>> What do you think?
>>>
>>> Cheers,
>>> Andreas
>>
>> I would like to resume this discussion on the occasion of a new [shameless
>> plug] package PAPPL that is to be packaged, see also [1], from the point
>> before discussion went off on an X-Y categories tangent.
>>
>> Here's a list of suggestions made for a new category so far, ordered from
>> (seemingly) best- to least-liked:
>>
>> media-print
>> sys-print
>> app-print(ing)
>
> IMHO sys-print is the best variant, since printing often requires
> system privileges to set it up or change lots of settings.
>
> Best regards,
> Andrew Savchenko
Maybe consider three new top-level categories?:
- print-drivers
- print-filters
- print-misc
Breaking out what's in the current net-print:
print-drivers/
brlaser
cndrvcups-common-lb
cndrvcups-lb
cnrdrvcups-lb
cups-windows
dymo-cups-drivers
epson-inkjet-printer-escpr
foo2zjs
gutenprint
hplip
hplip-plugin
kyocera-1x2x-mfp-driver
pnm2ppa
splix
print-filters/
apsfilter
c2esp
cnijfilter2
cups-filters
kyocera-mita-ppds
lexmark-upd-ppd
foomatic-db
foomatic-db-engine
foomatic-db-ppds
print-misc/
cups
cups-bjnp
cups-pdf
cups-pk-helper
fax4cups
gtklp
ink
libinklevel
mtink
npadmin
poster
sshlpr
I haven't looked at any of the other existing categories and only sorted out
net-print packages into these new proposed categories, but I think *most*
printing stuff is going to fall into one of those three type of buckets. A
fourth category, say print-scanning, may be able to be created specific to
scanning stuff, since that kinda has its own side-ecosystem. If we
accumulate enough printing-related libraries, I guess print-libs may also
come into being (right now, I put libinklevel under print-misc since it's
the only lib* standout).
Idea behind a new top-level print-* group of categories is that printing is
a fairly large ecosystem, and lumping it all into something like media-print
or sys-print seems to miss the mark a bit. media-* seems more aligned to
things like sound, video, and graphics (the digital kind), and less about
print media. sys-print implies the system-level connections that a printer
has, and would be a good fit for all of the printer driver packages, but not
as good a fit for things like net-print/poster.
Also, the HOMEPAGE for foo2zjs is dead and up for sale. That needs to be
changed to:
https://github.com/koenkooi/foo2zjs
--
Joshua Kinard
Gentoo/MIPS
kumba@gentoo.org
rsa6144/5C63F4E3F5C6C943 2015-04-27
177C 1972 1FB8 F254 BAD0 3E72 5C63 F4E3 F5C6 C943
"The past tempts us, the present confuses us, the future frightens us. And
our lives slip away, moment by moment, lost in that vast, terrible in-between."
--Emperor Turhan, Centauri Republic
next prev parent reply other threads:[~2021-12-18 0:37 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 21:47 [gentoo-dev] Printer drivers and net-print Andreas K. Huettel
2017-02-20 22:02 ` M. J. Everitt
2017-02-20 22:11 ` Matthew Thode
2017-02-21 8:28 ` Kristian Fiskerstrand
2017-02-21 8:53 ` Lars Wendler
2017-02-21 10:57 ` Ulrich Mueller
2017-02-22 1:05 ` M. J. Everitt
2017-02-22 2:48 ` Gordon Pettey
2017-02-22 3:08 ` M. J. Everitt
2017-02-22 12:29 ` Kent Fredric
2017-02-22 6:10 ` Ulrich Mueller
2017-02-22 21:08 ` Andrew Savchenko
2017-02-23 17:50 ` Ulrich Mueller
2017-02-23 20:58 ` Andrew Savchenko
2017-02-23 21:16 ` Ciaran McCreesh
2017-02-26 10:54 ` Andrew Savchenko
2017-02-26 14:55 ` Gordon Pettey
2017-02-27 21:16 ` Andrew Savchenko
2017-02-27 2:30 ` NP-Hardass
2017-02-27 10:04 ` Kristian Fiskerstrand
2017-02-27 20:44 ` Andrew Savchenko
2017-02-27 21:35 ` Mike Gilbert
2017-02-28 2:00 ` Kent Fredric
2017-02-28 8:47 ` Kristian Fiskerstrand
2021-12-17 13:00 ` Andreas Sturmlechner
2021-12-17 16:55 ` Ulrich Mueller
2021-12-17 16:56 ` Andrew Savchenko
2021-12-18 0:37 ` Joshua Kinard [this message]
2021-12-19 0:19 ` Andreas K. Huettel
2021-12-19 1:21 ` Joshua Kinard
2021-12-19 10:30 ` Ulrich Mueller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5debb049-dfed-e5ae-f8b1-539fa303f326@gentoo.org \
--to=kumba@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox