Summary: | GURU Access Request and General Ebuild Question | ||
---|---|---|---|
Product: | GURU | Reporter: | dev.tqb0k |
Component: | Access requests | Assignee: | GURU project: Gentoo devs <guru-devs> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | andrewammerlaan, dev.tqb0k, lssndrbarbieri, mgorny |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
dev.tqb0k
2023-08-05 07:59:19 UTC
> do I have to cram everything that needs to be fetched online in SRC_URI? I've written some other ebuilds but can't seem to get ones that require Node dependencies to work; I some variant of a "fetch error" every time - am I doing something wrong here?
Yes, the ebuild runs in a network sandbox to ensure reproducibility. Node is a bit difficult for this reason, but I believe we have some eclass in ::guru that you can use to make this work. I have never done this myself but you can ask for help on IRC or check the in-eclass documentiation (if there is any).
You don't need to "request PR access". That said, I don't think we really do much work using PRs — we instead give committers push access and let them push directly. Hello gentlemen - Andrew, Michał, thank you both for your quick and informative responses. Being that GURU doesn't use PRs, then I'd to to request commit access; what must I do to attain these permissions? Thanks, whichtux on GitHub The list's on the wiki: https://wiki.gentoo.org/wiki/Project:GURU/Information_for_Contributors#Prior_setup Hello Mr. Górny, Thank you for the information, I'll try this out in a few to check if everything checks out for me. Also, hats off to you, sir, for serving the Gentoo community for all these years; your contributions are very much appreciated! Yours truly, whichtux |