Re: Using smart within an SDK

[ChenQi <Qi.Chen@windriver.com>]

Hi Ash,

SDK has basically two parts, nativesdk part and the target part.
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.

Best Regards,
Chen Qi

On 05/14/2015 08:51 AM, Ash Charles wrote:
> Hi,
>
> I'd like to be able install packages using smart within an SDK
> environment (much like [1]; @Erik, did you find a solution?).
>
> I stumbled on two questions in looking into this.
>
> 1. Why does the nativesdk version of smart get wrapped with these
> environment variables, 'RPM_USRLIBRPM', 'RPM_ETCRPM', and
> 'RPM_LOCALEDIRRPM'?  As per [2], the RPM utilities themselves are
> already wrapped.  It might be nice to specify the '--data-dir'
> argument to smart with a create_cmdline_wrapper instead.
>
> 2. Why does the smart configuration data get removed during SDK
> creation?  In particular, the self.target_pm.remove_packaging_data
> line in meta/lib/oe/sdk.py.
>
> [1] https://lists.yoctoproject.org/pipermail/yocto/2015-March/024152.html
> [2] http://lists.openembedded.org/pipermail/openembedded-core/2012-December/071894.html
>
> Thanks for any advice!
> --Ash