Hi,
I'm looking to use a bbappend to add a repository/channel that the
smart package manager can use out of the box. For zypper, this was
just a question of adding a configuration file to the recipe.
How might I preconfigure Smart? The only way I've come up with so far
is a postinst 'smart cha
rtpm_1.4.1.bbappend
- this worked:
https://github.com/gumstix/meta-gumstix-extras/commit/acff007afffb19269e21bfd4cc1398fe23f00160
Hurrah!
--Ash
On Thu, Jul 25, 2013 at 2:24 AM, Paul Eggleton
wrote:
> Hi Ash,
>
> On Wednesday 24 July 2013 18:59:30 Ash Charles wrote:
>> I'm look
Hi,
I'm seeing warnings like
"
WARNING: The recipe linux-firmware is trying to install files into a
shared area when those files already exist. Those files and their
manifest location are:
/home/ash/Store/Yocto/yocto/build/tmp/sysroots/overo/lib/firmware/whiteheat.fw
Matched in manifest-ove
Hi Khem,
Thanks for your response.
On Thu, Feb 27, 2014 at 4:26 PM, Khem Raj wrote:
> it seems this module is installing/overwriting a file thats coming
> from some other recipe
> that you omitted from the errors above so cant tell which one exactly.
I've posted a more complete log: http://pasteb
On Thu, Feb 27, 2014 at 4:54 PM, Khem Raj wrote:
> as you can see kernel-firmware-whiteheat is the package name under
> which kernel is packaging it
> so include that if you want the kernel provided one.
Ah---perfect. That makes sense.
I had
MACHINE_EXTRA_RDEPENDS += "linux-firmware-sd8686"
I sho
;t populate any firmware
Am I on the right track?
--Ash
On Thu, Feb 27, 2014 at 5:09 PM, Ash Charles wrote:
> On Thu, Feb 27, 2014 at 4:54 PM, Khem Raj wrote:
>> as you can see kernel-firmware-whiteheat is the package name under
>> which kernel is packaging it
>> so includ
!
--Ash
On Fri, Feb 28, 2014 at 10:45 AM, Ash Charles wrote:
> I think my response yesterday was slightly premature...
>
> If I understand correctly, packages of the form
> 'kernel-firmware-' are provided by the kernel recipe for any
> firmware that is licensed such that it
Hi,
In my Yocto build, the RPM package for gettext-dev has a depency on an
apparently non-existent package "libgettextlib-dev". In the generated
pkgdata/runtime/gettext-dev file, I see
"RRECOMMENDS_gettext-dev: libgettextlib-dev libgettextsrc-dev
glibc-dev expat-dev".
>From the gettext recipe,
On Wed, Apr 8, 2015 at 11:54 PM, Khem Raj wrote:
> its probably due to solib name renaming, which is debian thing.
> you just might kill this -dev package completely and just have gettext-dev
> have everything development related.
Hi Khem,
Thanks for your response. How would I go about killing t
Hi,
I'm hosting an RPM based package repository on a different server than
the build machine; I've been use the distro's version of the
createrepo tool to keep the package index up to date. The Yocto
version of the createrepo tool has some customizations notably adding
a 'missingok' flag to handl
On Fri, Apr 17, 2015 at 2:43 PM, Ash Charles wrote:
> 2. BBCLASSEXTEND nativesdk for createrepo and add it to the
> buildtools-tarball.bb recipe. This feels like the best option. But
> the python environment doesn't get picked up properly...e.g.
> Traceback (most recent cal
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
On Wed, May 13, 2015 at 7:26 PM, ChenQi 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 installatio
On Thu, May 14, 2015 at 7:54 PM, ChenQi wrote:
> 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.
Ah okay---that makes sense. Thanks.
>
> We are now working a new kind of SDK in OE. We call it extensible SDK.
On Mon, May 18, 2015 at 10:13 PM, wrote:
> The idea is that an sdk will comprise of a manifest(contains list of
> sstate items in the sdk) and some location that contains the items in the
> manifest. So to update the sdk you would run a command and give it the
> location of the manifest and sstat
On Tue, May 26, 2015 at 3:18 PM, Randy Witt
wrote:
> Did you source the environment-setup script? If so, what distro were you
> using?
Ubuntu 15.04 (Vivid-Vervet). I used an SDK created based on the
gumstix-console-image rather than a mainstream image from meta-yocto
so perhaps there is a particu
On Tue, May 26, 2015 at 4:04 PM, Randy Witt
wrote:
> It is a bit of a different workflow than we were initially looking at, but I
> don't see a reason we couldn't do it. The locked signatures file should be
> able to be a superset of items you would want, so theoretically if you only
> wanted item
Hi,
(apologies if this is the wrong list---I tried sending to the bitbake
list and got bounced)
Under what conditions can I change the content of layers without
affecting an ongoing bitbake?
On occasion, I find myself wanting to do git operations on my layers
while I've got a build going on. I'
Hi,
I have two kernels for my device: one is current mainline kernel and
one is an older kernel that supports magic proprietary hardware
acceleration blobs. Some developers want the modern kernel, others
need the hardware acceleration which means they need the older kernel
plus a bunch of out-of-
Hi,
In thinking about this a bit more (and struggling with all three
methods), I wonder that creating a separate machine type in much the
same fashion as crownbay and crownbay-noemgd is the way to go.
--Ash
On Tue, Jun 17, 2014 at 8:56 AM, Ash Charles wrote:
> Hi,
>
> I have two kerne
Hi Alex,
On Fri, Jun 13, 2014 at 1:49 PM, Alex J Lennon
wrote:
> I think these two lines in cogl-1.0.inc are causing mesa to be pulled in
> incorrectly, but I'm not sure what ERDEPENDS does...
>
> # Extra RDEPENDS for PACKAGECONFIG
> # This has to be explictly listed, because cogl dlopens the back
Hi,
Based on the yocto manual [1], it looks like "screen" is a valid
MACHINE_FEATURE and, in fact, it looks like some machines actually
call out this feature. That said, I can't actually see that this
MACHINE_FEATURE is used. I checked with buildhistory and some
grepping but maybe I missed somet
Thanks very much Saul (and thanks for the git tips).
I'll pull this MACHINE_FEATURE from my machines.
--Ash
On Tue, Jan 27, 2015 at 1:14 PM, Saul Wold wrote:
> On 01/27/2015 11:01 AM, Ash Charles wrote:
>>
>> Hi,
>>
>> Based on the yocto manual [1], i
Hi,
Why does the PATH variable in the dot.bashrc shipped by the base-files
not include 'sbin' paths? It seems like any interactive user should
be able to call e.g. 'ifconfig' informationally---they should, and
would still be, blocked from calling 'ifconfig eth0 up'
After looking at the PATH for
a uses
non-sbin path.
Cheers,
Ash
On Tue, Feb 3, 2015 at 2:40 AM, Paul Eggleton
wrote:
> Hi Ash,
>
> On Friday 30 January 2015 10:28:21 Ash Charles wrote:
>> Why does the PATH variable in the dot.bashrc shipped by the base-files
>> not include 'sbin' paths? It seems like
25 matches
Mail list logo
