From: Andreas Radke <andreas.radke@mailbox.org>
To: printing-architecture@lists.linux-foundation.org
Subject: Re: [Printing-architecture] Upcoming work for OpenPrinting: Printer (Scanner) Applications and IPP System Service
Date: Fri, 8 Nov 2019 11:57:51 +0100 [thread overview]
Message-ID: <20191108115751.54932beb@workstation64.local> (raw)
In-Reply-To: <20191108020631.GJ26703@shaftnet.org>
[-- Attachment #1: Type: text/plain, Size: 1289 bytes --]
Am Thu, 7 Nov 2019 21:06:31 -0500
schrieb Solomon Peachy <pizza@shaftnet.org>:
> On Thu, Nov 07, 2019 at 08:14:59PM +0100, Till Kamppeter wrote:
> > - Quick solution to not loose functionality/hardware support in a
> > Linux distribution when the first CUPS without PPD support appears
> > and some drivers are not yet converted.
>
> I think this should be the primary beneficiary. I'm personally not
> going to lose any sleep over already-abandoned proprietary drivers
> that were never really supported to begin with. :)
If some big player wants to keep PPD driver support alive they should
keep maintaining a cups 2.3.x fork until the last non-IPP driven device
is dead.
> > The preferable way are native IPP applications. Whenever possible,
> > especially for new drivers or for drivers which are actively
> > maintained, like Gutenprint or HPLIP this is the way to go.
>
> Absolutely.
>
IPP without any backward compatibility should be the preferred way to
go.
When cups 2.4.x will be out I will probably disable any ppd driven
driver support in Arch. Just to stop people using closed source driver
and to push open standards. Anything else will probably go into our
community maintained unsupported AUR repositories.
-Andy
Arch Linux
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-11-08 10:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 15:34 [Printing-architecture] Upcoming work for OpenPrinting: Printer (Scanner) Applications and IPP System Service Till Kamppeter
2019-11-07 16:49 ` Solomon Peachy
2019-11-07 19:14 ` Till Kamppeter
2019-11-08 2:06 ` Solomon Peachy
2019-11-08 10:57 ` Andreas Radke [this message]
2019-11-08 13:33 ` Solomon Peachy
2019-11-08 17:15 ` Michael Sweet
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=20191108115751.54932beb@workstation64.local \
--to=andreas.radke@mailbox.org \
--cc=printing-architecture@lists.linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.