[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Chicken-hackers] Re: Backdoor GPL in message-digest

From: Felix
Subject: Re: [Chicken-hackers] Re: Backdoor GPL in message-digest
Date: Tue, 24 Aug 2010 14:19:34 +0200 (CEST)

From: Alaric Snell-Pym <address@hidden>
Subject: Re: [Chicken-hackers] Re: Backdoor GPL in message-digest
Date: Tue, 24 Aug 2010 10:41:02 +0100

> What I'd love is to have optional dependencies listed in the egg
> metadata, and then a way in the egg of being able to cond-expand based
> on which dependencies are available and enabled. chicken-install
> should
> have some mechanism to "disable" optional dependencies even through
> they're installed, so it's easier to build the non-GPL version of the
> egg in testing :-)
> chicken-install might be extended with a 'viral' flag on an egg's
> license, and then compute a license for every *installed compiled
> egg*,
> which will be the intersection of the egg's own license and the viral
> licenses of all its dependencies, and a viral flag if the egg's own
> license is viral. This could be easily represented as a symbol (the
> egg's native license) and a list of viral licenses (which may include
> the egg's own license if it's viral, and which all dependent eggs
> inherit).

The .meta file contents' format is open, you can add all sorts of
information there. A first step would be to make `chicken-status' walk
the dependency chain of each installed extension and scream if an egg
depends directly or indirectly on a viral license.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]