public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andreas Sturmlechner <asturm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Printer drivers and net-print
Date: Fri, 17 Dec 2021 14:00:48 +0100	[thread overview]
Message-ID: <25230153.1r3eYUQgxm@tuxbrain> (raw)
In-Reply-To: <2225532.dXl5vgaOU9@pinacolada>

[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]

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)


I agree net-print should not remain after such a move.


[1] https://bugs.gentoo.org/829351

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

  parent reply	other threads:[~2021-12-17 13:01 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 [this message]
2021-12-17 16:55   ` Ulrich Mueller
2021-12-17 16:56   ` Andrew Savchenko
2021-12-18  0:37     ` Joshua Kinard
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=25230153.1r3eYUQgxm@tuxbrain \
    --to=asturm@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