From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Finer granularity for RSUGGEST
Date: Tue, 23 Sep 2008 13:03:41 +0200 [thread overview]
Message-ID: <gbaied$pgl$1@ger.gmane.org> (raw)
In-Reply-To: <48D8B75D.7030302@gmx.net>
Robert Schuster wrote:
> 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"
Not related to Hennings point, put overwriting PACKAGES the way pictured
about will break out nice -dev and -dbg dependency changing (among other
things). Only overwrite PACKAGES if you fully understand the
consequences, which I think no OE developer that isn't called 'RP" does :)
regards,
Koen
>
> LICENSE = "GPLv2"
> LICENSE_${PN}-data = "CC-BY-SA"
>
> Or am I missing an important point here?
>
> Regards
> Robert
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2008-09-23 11:07 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
2008-09-23 11:03 ` Koen Kooi [this message]
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='gbaied$pgl$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox