From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Tarek El-Sherbiny <tarek.elsherbiny@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Smart runtime package manager
Date: Mon, 06 Jan 2014 17:40:18 +0000 [thread overview]
Message-ID: <4512745.rGr4OXPTXM@helios> (raw)
In-Reply-To: <CAB3sqtbYhaF6_=WyiihN_kE5F7yRLL4p5-YH8B5VZMcLcSNMcA@mail.gmail.com>
On Monday 06 January 2014 17:27:20 Tarek El-Sherbiny wrote:
> On Mon, Jan 6, 2014 at 1:57 PM, Paul Eggleton <paul.eggleton@linux.intel.com
> wrote:
> > On Sunday 05 January 2014 14:20:40 Tarek El-Sherbiny wrote:
> > > I'm trying to learn how smart works. I've been successful to create a
> > > repo, update and install from it. Is there smart install option to force
> > > install all the more recent packages without having to type the package
> > > name for each individual package?
> > > Something like update all to bring the target up-to-date in single
> > > command.
> >
> > "smart upgrade" should do this.
>
> Thanks Paul.
> I have another question. For smart to detect a new package version is
> available I think I have to bump the PR of the recipe. If there is another
> package that depends on it "e.g statically linking the library" bitbake
> will rebuild it but it wont bump the PR automatically. Is there a
> mechanism for bumping the PR not only for the modified package but also for
> all the packages that depends on it?
Yes, you should enable the PR service:
http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#working-with-a-pr-service
Cheers,
Paul
PS: Please keep replies on the mailing list - thanks.
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2014-01-06 17:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-05 14:20 Smart runtime package manager Tarek El-Sherbiny
2014-01-06 13:57 ` Paul Eggleton
[not found] ` <CAB3sqtbYhaF6_=WyiihN_kE5F7yRLL4p5-YH8B5VZMcLcSNMcA@mail.gmail.com>
2014-01-06 17:40 ` Paul Eggleton [this message]
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=4512745.rGr4OXPTXM@helios \
--to=paul.eggleton@linux.intel.com \
--cc=tarek.elsherbiny@gmail.com \
--cc=yocto@yoctoproject.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.