From: Martin Jansa <martin.jansa@gmail.com>
To: Laurentiu Palcu <laurentiu.palcu@intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] sstate.bbclass: consider postinstall dependencies too
Date: Mon, 4 Mar 2013 12:48:15 +0100 [thread overview]
Message-ID: <20130304114815.GH3268@jama> (raw)
In-Reply-To: <513487B9.8000502@intel.com>
[-- Attachment #1: Type: text/plain, Size: 949 bytes --]
On Mon, Mar 04, 2013 at 01:38:33PM +0200, Laurentiu Palcu wrote:
>
>
> On 03/04/2013 01:13 PM, Martin Jansa wrote:
> > On Mon, Mar 04, 2013 at 10:56:12AM +0000, Richard Purdie wrote:
> >> On Mon, 2013-03-04 at 11:51 +0100, Martin Jansa wrote:
> >>> Shouldn't this list be defined in layer.conf like
> >>> SIGGEN_EXCLUDERECIPES_ABISAFE, so that other layers can extend that
> >>> list?
> >>
> >> I'm hoping we only have very small list of these problematic
> >> dependencies. If we end up with a large number of them then yes, we'd
> >> need to abstract it but I'd prefer to avoid that unless proven
> >> necessary.
> >>
> >> Is there a specific case you have in mind?
> >
> > Isn't systemd-systemctl-native another candidate to be included?
> >
> It looks like it should be in the list... I'll resend a new version.
what about all u-a-native implementations?
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-03-04 12:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 10:37 [PATCH] sstate.bbclass: consider postinstall dependencies too Laurentiu Palcu
2013-03-04 10:51 ` Martin Jansa
2013-03-04 10:56 ` Richard Purdie
2013-03-04 11:13 ` Martin Jansa
2013-03-04 11:16 ` Burton, Ross
2013-03-04 11:38 ` Laurentiu Palcu
2013-03-04 11:48 ` Martin Jansa [this message]
2013-03-04 12:09 ` Richard Purdie
2013-03-04 11:45 ` [PATCH v2] " Laurentiu Palcu
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=20130304114815.GH3268@jama \
--to=martin.jansa@gmail.com \
--cc=laurentiu.palcu@intel.com \
--cc=openembedded-core@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.