From: "M. J. Everitt" <m.j.everitt@iee.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Printer drivers and net-print
Date: Wed, 22 Feb 2017 03:08:38 +0000 [thread overview]
Message-ID: <4cb37ab6-ead0-9bf9-f722-f42976c96dff@iee.org> (raw)
In-Reply-To: <CAHY5MefXQfwfZrv1rhymckmkK9eoncZ--Acu=7QjVoiunxr+VA@mail.gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1584 bytes --]
On 22/02/17 02:48, Gordon Pettey wrote:
> On Tue, Feb 21, 2017 at 7:05 PM, M. J. Everitt <m.j.everitt@iee.org
> <mailto:m.j.everitt@iee.org>> wrote:
>
> On 21/02/17 08:53, Lars Wendler wrote:
> > On Mon, 20 Feb 2017 22:47:17 +0100 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.
> > Like I said in IRC, I'm all in favor of this. "media-print" seems
> > reasonable as I don't consider printing related packages being
> > system-relevant (and thus no sys-print).
> >
> >
> Maybe we can shoot for "app-print" .. its not really a system package
> any more than a networking one, nor a (multi-)media package per-se
> (cue
> bikeshed on what 'media' means) .. so perhaps just 'app-print' or
> 'app-printing' .. I dunno ..
>
>
> There is no requirement for category names to be x-y. Instead of
> forcing a prefix-suffix pattern that doesn't really fit, just call it
> "printing".
Whilst I don't think there is anything specified in PMS/devmanual ..
find me another category without X-Y pattern? I'm not sure about portage
internals, but there could be some exploiting of the fact this is
'normally' the case ..
I could, ofc, be mistaken ...
[-- Attachment #1.1.2: Type: text/html, Size: 2887 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2017-02-22 3:08 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 [this message]
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
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=4cb37ab6-ead0-9bf9-f722-f42976c96dff@iee.org \
--to=m.j.everitt@iee.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