On Wed, 8 Apr 2020 17:39:54 +
Peter Stuge wrote:
> E.g. for auditing the installed values of these could be worth a lot.
Only as far as analyising "why was this package installed, currently
the metadata says its un-audited!".
But for things like "affected by CVE/Bug", the very nature of
On Wed, 8 Apr 2020 16:34:52 -0400
Mike Gilbert wrote:
> This was requested to allow users to pass aribtrary arguments to meson.
>
> Signed-off-by: Mike Gilbert
> ---
> eclass/meson.eclass | 11 +++
> 1 file changed, 11 insertions(+)
>
> diff --git a/eclass/meson.eclass
On 2020-04-08 16:28, Marek Szuba wrote:
> using an OpenCL implementation which exclusively targets CPUs is of
> limited use.
Clarification on the above: I meant using an implementation of this sort
*in standalone mode* i.e. set as THE OpenCL implementation by
eselect-opencl. It has never been my
This was requested to allow users to pass aribtrary arguments to meson.
Signed-off-by: Mike Gilbert
---
eclass/meson.eclass | 11 +++
1 file changed, 11 insertions(+)
diff --git a/eclass/meson.eclass b/eclass/meson.eclass
index 3e3a2e2f7a2e..0932a7ed427f 100644
---
This mainly rearranges some code to make it easier to read.
Also changes the bare 'meson' call to 'meson setup'.
Signed-off-by: Mike Gilbert
---
eclass/meson.eclass | 30 --
1 file changed, 20 insertions(+), 10 deletions(-)
diff --git a/eclass/meson.eclass
Looks good to me. Thanks!
Kent Fredric wrote:
> Syntax above not expected verbatim, just food for thought,
I think this is a really good and useful idea. I would love to see it.
> the nature of this metadata is that it SHOULD NOT be in the ebuild
> itself, as it is inherently "repo based", the installed values of
>
On 2020-04-08 11:28, Marek Szuba wrote:
Pending maintainer's approval.
Signed-off-by: Marek Szuba
---
dev-libs/rocm-opencl-runtime/rocm-opencl-runtime-3.0.0.ebuild | 2 +-
dev-libs/rocm-opencl-runtime/rocm-opencl-runtime-3.1.0.ebuild | 2 +-
At least version 4.4.0.117 works fine with a loader, and in any case
using an OpenCL implementation which exclusively targets CPUs is of
limited use.
Pending maintainer approval, and letting the stable ebuild be.
Signed-off-by: Marek Szuba
---
Pending maintainer's approval.
Signed-off-by: Marek Szuba
---
dev-libs/rocm-opencl-runtime/rocm-opencl-runtime-3.0.0.ebuild | 2 +-
dev-libs/rocm-opencl-runtime/rocm-opencl-runtime-3.1.0.ebuild | 2 +-
dev-libs/rocm-opencl-runtime/rocm-opencl-runtime-3.3.0.ebuild | 2 +-
3 files changed, 3
Pending maintainer approval, and letting the stable ebuild be.
Signed-off-by: Marek Szuba
---
media-libs/mesa/mesa-20.0.4.ebuild | 2 +-
media-libs/mesa/mesa-.ebuild | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/media-libs/mesa/mesa-20.0.4.ebuild
Now that we have got two OpenCL ICD loaders in the tree, that
starting with version 3, virtual/opencl will only pull an ICD loader
rather than any specific implementation, and that we are in the process
of following the footsteps of OpenGL in migrating away from using
eselect to switch between
On Tue, 07 Apr 2020 14:44:04 +0100
Roy Bamford wrote:
> Gentoo must not single out any package for special treatment.
Indeed. Cases like this just demonstrate that something about the way
we do things is somehow inadequate.
The idea that "what we have works" is something we get away with,
On Tue, 7 Apr 2020 12:47:33 +0200
Thomas Deutschmann wrote:
> Sure, that could have banal reasons like "No one audited the Linux
> version yet". But in security you don't issue warnings if you aren't
> sure. Because if you make false statements people will no longer trust
> you. But trust is
14 matches
Mail list logo
