On Wed, Feb 20, 2013 at 8:17 AM, Diego Elio Pettenò <flamee...@flameeyes.eu> wrote: > On 20/02/2013 13:02, Rich Freeman wrote: >> I'm actually wondering if that makes sense with git when a specific >> commit is referenced, since everything is content-hashed anyway. >> Perhaps we just need to confirm that git actually checks the hash. > > The policy is also because any ebuild relying on a network service to > work cannot be assured to work at any point in time: not only it depends > on the network connection of the user, but it also depends on the > service to be available.
Makes sense in general. If there really are firmware blobs that are only available via git and which cannot be redistributed we might consider whether it makes sense to not support them entirely, or to force them to be masked. Dropping or masking the packages doesn't fix the fact that they require a network service to install - it just makes it harder to install the package. If a tarball exists or can be created that would be the best solution all-around, of course. Rich
