All of lore.kernel.org
 help / color / mirror / Atom feed
From: ChenQi <Qi.Chen@windriver.com>
To: Ash Charles <ashcharles@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Using smart within an SDK
Date: Fri, 15 May 2015 10:54:28 +0800	[thread overview]
Message-ID: <55555FE4.7060902@windriver.com> (raw)
In-Reply-To: <CAK8F28=iqLWycPRJtvbJ3cjHd04e-XvrQhqHQ0iC7xZ6ADrASA@mail.gmail.com>

On 05/15/2015 02:21 AM, Ash Charles wrote:
> On Wed, May 13, 2015 at 7:26 PM, ChenQi <Qi.Chen@windriver.com> wrote:
>> For the nativesdk part, we can use smart/rpm to manage packages. A long time
>> ago, I tried this out and succeeded.
>> However, for the target part, we cannot do the same thing as the rpm
>> database for the target part is not usable after installation. I once tried
>> to solve this problem but failed.
>> You can have a little try and if you have some good news, let me know.
> Thanks for your response.
>
> I've not been able to use smart to install packages even on the
> nativesdk part---could you explain your steps?

I can recall that I used something like `PSEUDO_xxx=xxx PSEUDO_xxx=xxx 
smart(or rpm?) ... --data-dir=xxx <command>'. But I don't remember 
whether I tweaked something else. Sorry :(
That's really a long time ago and I didn't write a document at the time.

> What are the barriers to using the RPM database for the target part?

The rpm database is not usable. You do a query to list files that a 
package installed and you will find all the paths are not correct.

We are now working a new kind of SDK in OE. We call it extensible SDK. 
By design, its components could be updated/installed/removed using 
sstate objects. The task is not completed yet, but we are working on it.

Regards,
Chen Qi

>
> --Ash
>
>



  reply	other threads:[~2015-05-15  2:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-14  0:51 Using smart within an SDK Ash Charles
2015-05-14  2:26 ` ChenQi
2015-05-14 18:21   ` Ash Charles
2015-05-15  2:54     ` ChenQi [this message]
2015-05-18 23:48       ` Ash Charles
2015-05-19  5:13         ` randy.e.witt
2015-05-22 22:24           ` Ash Charles
2015-05-26 22:18             ` Randy Witt
2015-05-26 22:38               ` Ash Charles
2015-05-26 23:04                 ` Randy Witt
2015-05-26 23:30                   ` Ash Charles

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=55555FE4.7060902@windriver.com \
    --to=qi.chen@windriver.com \
    --cc=ashcharles@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.