All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Meixner <jsmeix@suse.de>
To: printing-architecture@lists.linux-foundation.org
Subject: Re: [Printing-architecture] Automatic printer setup with Printer Applications
Date: Wed, 24 Feb 2021 15:46:36 +0100	[thread overview]
Message-ID: <3e467a3bd51a7bc8083e6f06532db4ad@suse.de> (raw)
In-Reply-To: <1099419D-7CC7-448C-84B1-5C35D75F7A03@msweet.org>


Hello,

On 2021-02-24 15:17, Michael Sweet wrote (excerpt):
> Right now, the *expected* behavior is that the user
> has a compatible IPP printer and they don't need any
> special software for it.  The *exception* is that a user
> has a printer that needs extra software.
...
> Note: I am fully aware that in the photo/art printing arena
> there are people that will still want to use Gutenprint
> or other special purpose software rather than the
> standard IPP interface - that's fine, and that is what
> the Printer Application is for in the long term.
> But those users are "experts" and will know how to install
> the application and configure it for their printer.

I like to add that in enterprise environments
automated printer setup is almost never needed.

So nowadays any further efforts for automated printer setup
could be mostly a waste of time - time that could be better
spend elsewhere (even if that is just more time for beer ;-)

The more I think about it the more I like the idea
to deprectate all printer setup tools and related stuff
except what CUPS itself provides.

For the exceptional cases only documentation should be sufficient
like "when you have 'ACME SpecialPrinter XL' do this and that".


Kind Regards
Johannes Meixner
-- 
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5 - 90409 Nuernberg - Germany
(HRB 36809, AG Nuernberg) GF: Felix Imendoerffer

  reply	other threads:[~2021-02-24 14:46 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-23 19:27 [Printing-architecture] Automatic printer setup with Printer Applications Till Kamppeter
2021-02-24  7:37 ` Johannes Meixner
2021-02-24  8:03 ` Zdenek Dohnal
2021-02-24 11:25   ` Till Kamppeter
2021-02-24 12:01     ` Johannes Meixner
2021-02-24 13:51       ` Till Kamppeter
2021-02-25 10:30         ` Johannes Meixner
2021-02-25 13:37           ` Till Kamppeter
2021-02-25 14:00             ` Johannes Meixner
2021-02-25 13:53           ` Michael Sweet
2021-02-24 12:48     ` Solomon Peachy
2021-02-24 14:01       ` Johannes Meixner
2021-02-24 17:23         ` Till Kamppeter
2021-02-26  9:17           ` Johannes Meixner
2021-02-24 14:17       ` Till Kamppeter
2021-02-25 15:28         ` Solomon Peachy
2021-02-25 22:54           ` Till Kamppeter
2021-02-26 14:59             ` Solomon Peachy
2021-02-25  8:28       ` Zdenek Dohnal
2021-02-25 14:54         ` Solomon Peachy
2021-02-26 10:03           ` Johannes Meixner
2021-02-26 12:28             ` Solomon Peachy
2021-02-27 21:07               ` Michael Sweet
2021-02-24 14:17 ` Michael Sweet
2021-02-24 14:46   ` Johannes Meixner [this message]
2021-02-24 18:47     ` Till Kamppeter
2021-02-24 17:40   ` Till Kamppeter
2021-02-24 17:48     ` Michael Sweet
2021-02-24 19:21       ` Till Kamppeter
2021-02-24 20:01         ` Michael Sweet
2021-02-24 20:15           ` Till Kamppeter
2021-02-25  8:52   ` Zdenek Dohnal
2021-02-25  9:24     ` Till Kamppeter
2021-02-25  9:54       ` Zdenek Dohnal
2021-02-25 13:43       ` Michael Sweet
2021-02-25 19:39         ` Till Kamppeter
2021-02-25 13:33     ` Michael Sweet
2021-02-25 15:24       ` Till Kamppeter
2021-02-25 15:30         ` Michael Sweet
2021-02-25 21:51           ` Till Kamppeter
2021-03-02 10:58 ` [Printing-architecture] Future of Printer Setup Tools Till Kamppeter
2021-03-02 12:04   ` Johannes Meixner
2021-03-02 22:52     ` Till Kamppeter

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=3e467a3bd51a7bc8083e6f06532db4ad@suse.de \
    --to=jsmeix@suse.de \
    --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.