Hi,
I am using a build environment based on the yocto project from one of
the big HW suppliers in the mobile industries. They are continuously
breaking the principles behind the yocto project and at one point they
managed to break the sstate cache because they are doing things in
there own way
Thanks Alex,
When I do a factory reset, the system detects as a first boot and the
script is executed.
> cat /var/log/postinstall.log
Configuring test-deployment.
One thing which puzzles me: the /etc/ipk-postinsts directory do not exist.
Not in the image recipe folder, not in the image file
On Wed, 13 May 2020, Richard Leitner wrote:
> On Wed, May 13, 2020 at 12:39:44PM +0200, Quentin Schulz wrote:
> > On Wed, May 13, 2020 at 06:25:01AM -0400, Robert P. J. Day wrote:
>
> ...
>
> > If it's really widely used, maybe something to add to
> > openembedded-core/files/common-licenses/ ? So
Hi,
On Wed, May 13, 2020 at 10:36:49AM +0200, Mans Zigher wrote:
> I am using a build environment based on the yocto project from one of
> the big HW suppliers in the mobile industries. They are continuously
> breaking the principles behind the yocto project and at one point they
> managed to
On Wed, May 13, 2020 at 12:39:44PM +0200, Quentin Schulz wrote:
> On Wed, May 13, 2020 at 06:25:01AM -0400, Robert P. J. Day wrote:
...
> If it's really widely used, maybe something to add to
> openembedded-core/files/common-licenses/ ? So that you don't need any of
> the suggested ways?
+1 for
On Wed, 13 May 2020, Quentin Schulz wrote:
> Hi Robert,
>
> On Wed, May 13, 2020 at 07:19:59AM -0400, Robert P. J. Day wrote:
> > On Wed, 13 May 2020, Richard Leitner wrote:
> >
> > > On Wed, May 13, 2020 at 12:39:44PM +0200, Quentin Schulz wrote:
> > > > On Wed, May 13, 2020 at 06:25:01AM -0400,
Hi Robert,
On Wed, May 13, 2020 at 07:19:59AM -0400, Robert P. J. Day wrote:
> On Wed, 13 May 2020, Richard Leitner wrote:
>
> > On Wed, May 13, 2020 at 12:39:44PM +0200, Quentin Schulz wrote:
> > > On Wed, May 13, 2020 at 06:25:01AM -0400, Robert P. J. Day wrote:
> >
> > ...
> >
> > > If it's
What are some nasty hack options?
The major surgery would be less maintainable.
On Wed, May 13, 2020, 12:51 PM Ross Burton wrote:
> On Wed, 13 May 2020 at 20:28, Joel Winarske
> wrote:
> > In this case I already have a Target and Native recipe. The Project
> generates a Native artifact when
On Wed, 13 May 2020 at 20:28, Joel Winarske wrote:
> In this case I already have a Target and Native recipe. The Project
> generates a Native artifact when building the Target. Not resolvable without
> major surgery. This artifact is then required in other Target recipes.
A target recipe
On Wed, 13 May 2020 at 21:05, Joel Winarske wrote:
> What are some nasty hack options?
Putting files in the target sysroot that are in fact native binaries.
Don't do that.
> The major surgery would be less maintainable.
Can you not work with upstream to integrate the changes?
Alternatively, if
Reading recipes-devtools/run-postinsts/run-postinsts/run-postinsts
and_save_postinsts_common (in rootfs.py) once more, it seems
/etc/ipk-postinsts is only used if there is no package manager on the
target.
If there is, then 'opkg configure' is run directly, and so postinsts come
from some
colleague added a new recipe to a build, got a warning "The license
listed Unlicense was not in the licenses collected for recipe
python-filelock" and, sure enough, that source was released under the
"Unlicense" which i had never heard of:
Hi Robert,
On Wed, May 13, 2020 at 06:25:01AM -0400, Robert P. J. Day wrote:
>
> colleague added a new recipe to a build, got a warning "The license
> listed Unlicense was not in the licenses collected for recipe
> python-filelock" and, sure enough, that source was released under the
>
OK I found.
Yes "opkg configure" will call /var/lib/opkg/info/*.postinst for packages
marked as "unpacked" in /var/lib/opkg/status ex:
Package: test-deployment-lic
Version: 1.0-r0
Status: install ok unpacked
Architecture: aarch64
Installed-Time: 1589349316
Auto-Installed: yes
After update
On Wed, 13 May 2020, Quentin Schulz wrote:
... snip ...
> If it's really widely used, maybe something to add to
> openembedded-core/files/common-licenses/ ? So that you don't need
> any of the suggested ways?
that was one of the first things that came to mind ... if there are
enough packages
On Wed, May 13, 2020 at 08:40:28AM -0400, Robert P. J. Day wrote:
> On Wed, 13 May 2020, Quentin Schulz wrote:
>
> > Hi Robert,
> >
> > On Wed, May 13, 2020 at 07:19:59AM -0400, Robert P. J. Day wrote:
> > > On Wed, 13 May 2020, Richard Leitner wrote:
> > >
> > > > On Wed, May 13, 2020 at
On Wed, 13 May 2020, Quentin Schulz wrote:
> On Wed, May 13, 2020 at 08:40:28AM -0400, Robert P. J. Day wrote:
> > On Wed, 13 May 2020, Quentin Schulz wrote:
> >
> > > Hi Robert,
> > >
> > > On Wed, May 13, 2020 at 07:19:59AM -0400, Robert P. J. Day wrote:
> > > > On Wed, 13 May 2020, Richard
On Wed, May 13, 2020 at 09:53:12AM -0400, Robert P. J. Day wrote:
[...]
>
> it gets weirder ... the project i'm working with is based on morty
> so that variable *would* still be relevant, but even adding
> "Unlicense" to that variable didn't stop the offending recipe
> from still generating a
Hello,
We are pleased to announce the meta-intel 13.0 layer for the Yocto Project 3.1
"dunfell" release is now available for download.
Thank you for everyone's contributions to this release.
Vineela Tummalapalli
Intel Corporation
--
13.0-dunfell-3.1 Release Notes
19 matches
Mail list logo
