Hi Haelwenn,
On 3/27/20 1:50 AM, Haelwenn (lanodan) Monnier wrote:
> Couldn't the snapd_${PV}.vendor.tar.xz available in
> https://github.com/snapcore/snapd/releases
> work in your case to avoid downloading tarballs?
> And probably consider using go-modules.eclass, which can also allow
> packaging when there is no vendoring done by the upstream by just
> cut(1)'ing the content of go.sum
I'm using the archive tarball... You're right I will try it instead and
thanks for the heads-up about controlling the content of go.sum using
go-modules.eclass.
> And I'm not so sure why you want to apparently host a tarball?
> Maybe you're not aware that SRC_URI accepts multiple tarballs? And
> btw you strongly should only use upstream URLs in it, they don't
> need to be mirrored in distfiles.gentoo.org for the ebuild to work.The reason to host the tarball was regarded to my understanding of requirements pointed out in src_test[1] function notes about network sandbox. Not related to the build process, but thinking on an environment with restricted proxy access to only trusted locations there would be probably a limitation to access any url. So for distributing additional sources behind well known places such as gentoo mirrors, github or gitlab could be an issue. What do you think about this? Thanks [1] https://devmanual.gentoo.org/ebuild-writing/functions/src_test/index.html
signature.asc
Description: OpenPGP digital signature
