TrueCrypt and it's lovely license
-----BEGIN PGP SIGNED MESSAGE-----
I just became aware of  today.
Several months ago, after a conversation with upstream and a couple
other devs, I decided to remove the RESTRICT="mirror fetch" parts.
Upstream didn't appear worried about the mirroring, but rather that they
wanted people to accept their license. So I left in RESTRICT="bindist"
and the ewarn about the license.
Given what I read on that bug today, would it be better if I went back
to RESTRICT="mirror fetch"? Or should I perhaps be doing something
entirely different? Perhaps make it so that the user has to add that
license to package.license?
@Trustees: Any thoughts? I didn't mean to step on any toes, I just
hadn't spotted that old bug until today.
Dane Smith (c1pher)
Gentoo Linux Developer -- QA / Crypto / Sunrise / x86
RSA Key: http://pgp.mit.edu:11371/pks/lookup?search=0x0C2E1531&op=index
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
|All times are GMT. The time now is 01:58 AM.|
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.