From: Joshua Lock
Build and install libgs library, which is a build dependency
of a few other libraries, such as libspectre.
We don't want to ship the executable binaries, only the library and its
headers, hence oe_runmake install-so + rm -rf, not e.g. oe_libinstall.
Signed-off-by: Joshua Lock
* Trevor Woerner [170228 19:01]:
> Ideally "devtool add ..." wouldn't choke and crash when it encounters a
> LICENSE string it doesn't understand. When parsing license strings from random
> places on The Internet it's inevitable odd things will come up :-)
I recently also stumbled upon this. I'v
* Khem Raj [170303 02:18]:
> On Wed, Mar 1, 2017 at 9:19 AM, Anders Darander wrote:
> > Quite a few npm packages declare MIT/X11 as their license. This is equal to
> > a pure MIT license.
> it would be good if you could attach a link where this can be referred to.
Sure, I'll try to find a good
Hi,
* Paul Eggleton [170302 02:44]:
> On Thursday, 2 March 2017 6:19:55 AM NZDT Anders Darander wrote:
> > NpmRecipeHandler(RecipeHandler):
> > def get_npm_package_dependencies(self, pdata):
> > dependencies = pdata.get('dependencies', {})
> > optionalDependencies = pdata.
From: "Chang, Rebecca Swee Fun"
Hi all,
This is an version upgrade for OpenSSL from 1.0.2h to 1.0.2k.
The upgrade was forklifted from OE-Core master branch to
Jethro branch and remove upstream dependencies to new bbclasses.
The details of CVEs are mentioned in the patch commit message.
The mai
Ross,
Good point!
I thought it was possible to have an implementation of libGL.so without
X11, for example by using Wayland or any other Window System, I didn't
know that the libGL was tied to X11 (on Linux). Also, I didn't see any
specific X11 code in the libGLU so I was a bit confused by th
On 4 March 2017 at 22:52, Gabriel Huau wrote:
> I'm not sure to understand why do we have a dependency on X11 in the
> libGLU package? I might miss some pieces of information here, but IMO, it
> should only depends on opengl as the libGL.so could be generated without
> X11 or any Window system.
>
On Sun, 2017-03-05 at 10:40 +0100, Nicolas Dechesne wrote:
> hi,
>
> I am trying to understand why the systemd recipe creates an
> empty /etc/machine-id file:
>
> # Create machine-id
>
> # 20:12 < mezcalero> koen: you have three options: a) run
> systemd-machine-id-setup at install ti
hi,
I am trying to understand why the systemd recipe creates an empty
/etc/machine-id file:
# Create machine-id
# 20:12 < mezcalero> koen: you have three options: a) run
systemd-machine-id-setup at install time, b) have / read-only and an empty
file there (for stateless) and c) boot with / writa
