-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/20/2013 02:55 AM, Ulrich Mueller wrote:
I am going to respond here because it makes the most sense to me. > I mostly agree. However, there are not two, but three classes of > licenses for firmware images: > > 1. Free software > 2. Non-free, but can be redistributed > 3. Cannot be redistributed > > The split between 2 and 3 is the more important one, because we cannot > mirror things under 3. I completely agree. I will HAPPILY divide the ebuild up with a nonfree (or other suggested SANE use flag) to denote the difference between 1 and 2. None of this is under contest, this choice is all but too easy. Depending on the licensing issues which arise I may even add in a separate ebuild. The issue come in with number 3. Adding a bindist use flag for the - -9999 ebuild seems sane since it pulls from git and we don't have to redist it, but is is possible to RESTRICT="bindist? bindist" ? Anyone volunteering to tear through this licensing mess and start breaking things into groups? - -Zero -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRJPedAAoJEKXdFCfdEflKhIUQAKXMr8tpwhrFBh2/LxfsdVRQ n6F72a2KCHyM2YCCQsw3eKskBKmeawQNNKWAQmOaDjn6dcEVi0hxHBLr42m3CZiL yNA9PRAvRSyshEn8NN/ExTR4eGZft2XqPuhszN129Eu3pJknvKQaPy5ItNzORzN0 FJDherBc2DXs4Uc0VmKxezHxNZZwv1OHIRPtNFGTDy4Eixw4GCYOEg8u1yI23iz7 p+Ef2YjoJPqs9Q3zxuFuJ/is9tIcKdzRy7kNXne92BCvVIst5Dflgg6kQ925eoaM RifTXv6w1cinItrBRzITftS6j44CcZVpYyRye1ganwuLb90Cxb5U2x8wsj6a1Tcu okVMWk/ncAHvjrkVoC1/wSpjyCgL5J2EaY5C5O5kkhPxNhwjfICpppawGR7psxAJ EQjl+u8O6HlVVbPIHTKGlEtSG+HGxVrVX5+CNj39MHEVIhqqVkvw+UenG4lG/Dv8 T+uAjTMYXJzMcVcw90hg8vHmygjXDwIypf0VGf4h+RCloX92dCP5HeBaU79/18Gz cGfdnOlSsUG7dr+VG4g7O+4AsopNbRe+a2EugGSMQ5IjkK7TaCYFt7K0nKbVYVyt AeMhsU17/X15rUpYNv37Liu4ythXyldVQMpnvclbx/kwiPR1bK3XSZfvZOX0g5Rb E2snaN0NNWWCIoj4aK1r =BJk0 -----END PGP SIGNATURE-----
