On Fri, 2020-03-27 at 01:16 +0000, Samuel Bernardo wrote: > Dear all, > > Fulfilling the linting of ebuild code style design for software projects > that loads their dependencies during build, such as go based projects or > npm as an example, could be very nasty. > > Looking into source code of snapd or opennebula as two examples, I need > to break network sandbox to get all dependencies for snapd go modules or > opennebula sunstone npm code. >
Stop here. If you think that you need to 'break network sandbox', you already have the wrong attitude and shouldn't continue. Network sandbox is not your enemy. Using network is. Network sandbox protects users from paying extra because you've written a bad ebuild that unexpectedly downloads lot of data on their mobile connection. Network sandbox makes sure that we don't end up delivering stuff that doesn't work to people who are on isolated networks or simply have non-permanent connections. Network sandbox makes sure that these ebuilds will work three months from now when upstream randomly decides to remove old files or shuffle servers, or just get hits by a temporary issue. There's no 'breaking the network sandbox'. You must fix the ebuild not to require Internet. -- Best regards, Michał Górny
signature.asc
Description: This is a digitally signed message part
