All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: "Wichmann, Mats D" <mats.d.wichmann@intel.com>
Cc: printing-architecture@lists.freestandards.org,
	lsb-discuss <lsb-discuss@lists.freestandards.org>
Subject: Re: [Printing-architecture] [lsb-discuss] Distribution-independent printer driver package --first shot
Date: Mon, 05 Feb 2007 17:09:30 +0000	[thread overview]
Message-ID: <45C764CA.4070000@gmail.com> (raw)
In-Reply-To: <3F62CBEE02D6404E98C65934617EB58201949FE6@fmsmsx414.amr.corp.intel.com>

Wichmann, Mats D wrote:
>> I have intendedly left it out as the LSB Build Environment 
>> does not have an "lsb" package installed. It should have such a package
> 
>> (meta-package?) installed so that you can install LSB packages in it.
> 
> At least the lsb sample implementation (lsbsi) does or should
> have this.  I'm not sure of the thinking behind leaving it
> of the buildenv, if it wasn't just an omission. Wouldn't hurt
> to file a bug on this as a reminder.
>

On the sample implementation the RPM installation does not complain 
about missing PPDs, but about missing directories:

------------------------------------------------------------------------
bash-3.1# rpm -Uvh /tmp/work/splix-1.0.1-0.beta2.1lsb3.1.i486.rpm
error: Failed dependencies:
         /opt is needed by splix-1.0.1-0.beta2.1lsb3.1.i486
         /opt/lib/printdriver is needed by splix-1.0.1-0.beta2.1lsb3.1.i486
         /opt/share/ppd is needed by splix-1.0.1-0.beta2.1lsb3.1.i486
bash-3.1#
------------------------------------------------------------------------

Once RPM should simply create the directories and not complain, and 
second, all the directories are there, I have created them before trying 
to install the RPM.

>> Why can I not use "Requires lsb >= 3.1", are the LSBs not backward 
>> compatible?
> 
> You can and should - at least at the moment when there's no
> such thing as a 3.2.  pkgchk is saying it didn't see this...
>

I have changed it to "lsb >= 3.1" now.

    Till


       reply	other threads:[~2007-02-05 17:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3F62CBEE02D6404E98C65934617EB58201949FE6@fmsmsx414.amr.corp.intel.com>
2007-02-05 17:09 ` Till Kamppeter [this message]
     [not found] <3F62CBEE02D6404E98C65934617EB5820194A075@fmsmsx414.amr.corp.intel.com>
2007-02-05 17:53 ` [Printing-architecture] [lsb-discuss] Distribution-independent printer driver package --first shot Till Kamppeter
     [not found] <3F62CBEE02D6404E98C65934617EB58201949F94@fmsmsx414.amr.corp.intel.com>
2007-02-05 16:32 ` 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=45C764CA.4070000@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=lsb-discuss@lists.freestandards.org \
    --cc=mats.d.wichmann@intel.com \
    --cc=printing-architecture@lists.freestandards.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.