One more thing that came to my mind is that the project is missing demo
recipes/real life examples in core that actually would show that one can
achieve reproducibility in the sense of the project's definition for
both npm and go.
So far there is the fetcher code but real life users are living
On 25.12.21 20:32, Stefan Herbrechtsmeier wrote:
Isn't the circular dependencies problem mainly a problem of the native
packages? In many cases the dependency only exists at compile time of
the main project and not at compile time of the dependency itself. In
case of a native package all
What I so far don't really get is why increase in parsing time is such a
big deal.
I admit when we're talking about npm it's some kind of a drastic
increase in recipes one would have to maintain, just because some random
project decides to use a trillion dependencies instead of writing two or
On Sat, 25 Dec 2021 at 20:32, Stefan Herbrechtsmeier <
ste...@herbrechtsmeier.net> wrote:
> > I'm not sure how to deal with that, so there aren't that many options
> here.
>
> This is a common problem for all language specific package managers
> (python / pip, Node.js / npm, Rust / Carge, go) and
On Fri, Dec 24, 2021 at 2:36 AM Konrad Weihmann wrote:
>
> I had a look at the failures and most of them are fairly easy to fix -
> all but the go recipes like influxdb.
>
> I'm not sure how to deal with that, so there aren't that many options here.
>
> Either
> - inject all the needed with a
Hi Konrad,
Am 24.12.21 um 11:36 schrieb Konrad Weihmann:
I had a look at the failures and most of them are fairly easy to fix -
all but the go recipes like influxdb.
The go class doesn't work without network by default if the project
doesn't provide a vendor folder.
I'm not sure how to
Hi Richard,
Am 24.12.21 um 09:30 schrieb Richard Purdie:
On Thu, 2021-12-23 at 22:00 -0800, Khem Raj wrote:
is this list of failures due to this patch ?
https://errors.yoctoproject.org/Errors/Build/137579/
Looks likely, yes. Recipes shouldn't be attempting downloads in do_compile :(
In
Modify the testcases properly to generate expected output.
Upstream-Status: Backport
[https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=51c500269bf53749b107807d84271385fad35628]
Upstream-Status: Backport
[https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=bef32d4a28595e933f24fef378cf052a30b674a7]
