All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: Jeff Licquia <jeff@licquia.org>
Cc: printing-architecture@lists.linux-foundation.org,
	lsb-discuss@lists.linux-foundation.org
Subject: Re: [Printing-architecture] [lsb-discuss] LSB 4.0 and printing
Date: Wed, 26 Mar 2008 22:34:13 +0100	[thread overview]
Message-ID: <47EAC155.4040206@gmail.com> (raw)
In-Reply-To: <47EA99E8.8020007@licquia.org>

What can be added without problems is SANE, as this is in every common 
distro and with the strong trend on multi-function devices it is very 
important for hardware vendors to make driver packages. It also allows 
to expand the initiative on distribution-independent driver packages to 
scanners (including stand-alone devices).

Doing uplifts, like CUPS 1.1.x -> 1.2.x is not possible as LSB 4.0 is 
based on the same enterprise distros as 3.2. Why not 3.3 then? We should 
raise the major number for new enterprise distros as base and the minor 
for a new LSB based on the same enterprise distros. WDYT?

Any suggestions on what else to add to the printing requirements?

We will also talk in Austin on the joint session of LSB and OpenPrinting 
about that subject.

    Till

Jeff Licquia wrote:
> The LSB 4.0 project plan 
> (https://www.linux-foundation.org/en/ProjectPlan40) has this to say 
> about printing requirements:
> 
> "Requirements being worked on by Printing Workgroup."
> 
> So I'm checking to see if this is, in fact true.  Does the OpenPrinting 
> workgroup have any requirements they'd like to see in LSB 4.0?
> _______________________________________________
> lsb-discuss mailing list
> lsb-discuss@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/lsb-discuss
> 


       reply	other threads:[~2008-03-26 21:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <47EA99E8.8020007@licquia.org>
2008-03-26 21:34 ` Till Kamppeter [this message]
2008-03-27  8:48   ` [Printing-architecture] [lsb-discuss] LSB 4.0 and printing Klaus Singvogel
     [not found]   ` <Pine.LNX.4.64.0803271421320.19740@nelson.suse.de>
2008-03-27 14:19     ` Klaus Singvogel
2008-03-27 14:29       ` Till Kamppeter
     [not found]       ` <Pine.LNX.4.64.0803271527300.20593@nelson.suse.de>
2008-03-27 15:31         ` Klaus Singvogel
     [not found]           ` <Pine.LNX.4.64.0803271634280.23932@nelson.suse.de>
2008-03-27 16:55             ` Klaus Singvogel
2008-03-27 17:42               ` Ira McDonald
2008-03-27 22:57                 ` Till Kamppeter
2008-03-28 14:02                   ` Klaus Singvogel
     [not found]               ` <Pine.LNX.4.64.0803281008280.14927@nelson.suse.de>
2008-03-28 16:09                 ` Klaus Singvogel
2008-03-27 22:23     ` Till Kamppeter
     [not found]   ` <20080326222308.GB7202@mit.edu>
     [not found]     ` <3F62CBEE02D6404E98C65934617EB582040A7A41@fmsmsx414.amr.corp.intel.com>
     [not found]       ` <20080326232809.GD7202@mit.edu>
2008-03-27 23:04         ` 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=47EAC155.4040206@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=jeff@licquia.org \
    --cc=lsb-discuss@lists.linux-foundation.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.