From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] sstate: Implement a setscene dependency validation routine to allow skipping of some sstate installation
Date: Fri, 16 Nov 2012 16:12:40 +0000 [thread overview]
Message-ID: <1353082360.3709.108.camel@ted> (raw)
In-Reply-To: <CAP9ODKrfu8CMJ+ZWqkwQUCP+56WU_4sLf0Js9j_fYYGfDr7a0w@mail.gmail.com>
On Fri, 2012-11-16 at 13:58 -0200, Otavio Salvador wrote:
> On Fri, Nov 16, 2012 at 1:32 PM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> This is a first attempt at logic to determine when a sstate
> dependency needs
> to be installed and when it does not. Its a start at the logic
> and errs on the
>
> s/errs/errors/
It is actually meant to be errs :)
> + # do_package_write_* and do_package doesn't need
> do_package
> + if taskdependees[task][1] == "do_package" and
> taskdependees[dep][1] in ['do_package',
> 'do_package_write_deb', 'do_package_write_ipk',
> 'do_package_write_rpm']:
> + continue
>
> I understand why you does this but it would be better if we had a
> central place to have the do_package_write_$pkg recorded or when
> adding new type this could be forgotten.
Its a nice idea but I can't see any practical way to do this at the
moment.
Cheers,
Richard
next prev parent reply other threads:[~2012-11-16 16:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 15:32 [PATCH] sstate: Implement a setscene dependency validation routine to allow skipping of some sstate installation Richard Purdie
2012-11-16 15:58 ` Otavio Salvador
2012-11-16 16:09 ` Burton, Ross
2012-11-16 16:21 ` Otavio Salvador
2012-11-16 16:12 ` Richard Purdie [this message]
2012-11-16 16:22 ` Otavio Salvador
2012-11-16 16:31 ` Richard Purdie
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=1353082360.3709.108.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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