-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
im maintaining `di'. However, with the latest release, upstream decided
to completely switch over to `iffe' as configure replacement. `iffe' is
licensed by the AT&T Source code Agreement, which is, at least to my
knowledge, not considered dfsg compliant. As it stands, im not able to
use the old, dfsg-free scripts and to simply remove the non-free parts
from the tarball, like i did in the past.
Shipping iffe in the source tarball would not prevent any user from
deriving/modifying/patching `di' itself. As long as iffe doesn't get
installed as a package, nor is represented as being part of `di', I
don't see a problem, though. Please speak up :)
bye,
- michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFC61bjEFV7g4B8rCURAvdNAJ4gdWXfqgf9ZCD4EkD+wP5Valg0agCff2KI
ExPe/YgaGzwx8Wva5w6kOWs=
=7LlZ
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
