All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Schuster <theBohemian@gmx.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Finer granularity for RSUGGEST
Date: Tue, 23 Sep 2008 11:31:09 +0200	[thread overview]
Message-ID: <48D8B75D.7030302@gmx.net> (raw)
In-Reply-To: <20080922205525.GA23908@rhein.zuhause.netz>

[-- Attachment #1: Type: text/plain, Size: 1058 bytes --]

Henning Heinold schrieb:
> Hi,
> 
> after fiddling with a filesystem kernel modul and his tools I noticed
> in package_ipk.bbclass that if we set RSUGGESTS Variable the suggest field
> in the ipk is set for all packages even -doc -dbg -dev and self defined
> packages.  I personal
> think is not a good choice and way. In my example the kernel module only needs
> to suggest the tools package. And with the old method the tools package suggest
> it self.
> 
> I have prepared a patch for ipk and deb that let us set:
> 
> ${PN}_RSUGGESTS = mooo
I do not think this is a good idea. You can have the same effect just
now by doing

RSUGGEST_${PN} = "mooo"

Currently if you set a variable that affects the binary package you know
it will end up in all of the binary packages declared in PACKAGES. E.g.
MAINTAINER, DESCRIPTION, LICENSE and so on.

You can easily prevent this by doing:

PACKAGES = "${PN} ${PN}-data"

LICENSE = "GPLv2"
LICENSE_${PN}-data = "CC-BY-SA"

Or am I missing an important point here?

Regards
Robert


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 268 bytes --]

  reply	other threads:[~2008-09-23  9:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-22 20:55 Finer granularity for RSUGGEST Henning Heinold
2008-09-23  9:31 ` Robert Schuster [this message]
2008-09-23 11:03   ` Koen Kooi
2008-09-25 19:35   ` Henning Heinold

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=48D8B75D.7030302@gmx.net \
    --to=thebohemian@gmx.net \
    --cc=openembedded-devel@lists.openembedded.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.