From: Mathieu Lirzin <mthl@gnu.org>
To: Alex Vong <alexvong1995@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: octave license is incompatible with openssl
Date: Fri, 05 Aug 2016 13:43:16 +0200 [thread overview]
Message-ID: <87popnjvaj.fsf@gnu.org> (raw)
In-Reply-To: <87vazfd1tw.fsf@gmail.com> (Alex Vong's message of "Fri, 05 Aug 2016 17:03:55 +0800")
Alex Vong <alexvong1995@gmail.com> writes:
> John Darrington <john@darrington.wattle.id.au> writes:
>
>> I would not be at all suprised if there were more incompatibilities like
>> this. Ought we not have a lint rule that checks this?
>>
> Indeed, in the short term, we could lint for special case, such that
> openssl appears as an input for an GPLv[123](+) package.
>
>
> In the long term, we could have the following in guix. Since licenses
> are scheme values. I was thinking we can have procedure like:
>
> (compatible? l1 l2)
>
> which is a reflexive and symmetric relation. Also, we might be able to
> build compound licenses by:
>
> (dual-license lics ...)
>
> and
>
> (intersect-license lics ...)
>
> The 3 procedures should satisfy the following "laws":
>
> (compatible? l1 (dual-license lics ...))
>
> if and only if
>
> (any (cut compatible? l1 <>) lics)
>
> Similarly,
>
> (compatible? l1 (intersect-license lics ...))
>
> if and only if
>
> (every (cut compatible? l1 <>) lics)
>
>
> How do everyone think?
>
I like the idea!
--
Mathieu Lirzin
next prev parent reply other threads:[~2016-08-05 11:43 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 16:35 octave license is incompatible with openssl Alex Vong
2016-08-04 17:10 ` John Darrington
2016-08-04 17:20 ` ng0
2016-08-05 9:08 ` Alex Vong
2016-08-05 9:03 ` Alex Vong
2016-08-05 11:43 ` Mathieu Lirzin [this message]
2016-08-05 6:50 ` Ricardo Wurmus
2016-08-06 1:52 ` Alex Vong
2016-08-08 20:00 ` Leo Famulari
2016-08-09 16:00 ` Alex Vong
2016-08-09 17:27 ` Mike Miller
2016-08-09 18:30 ` Ricardo Wurmus
2016-08-09 21:33 ` kei
2016-08-10 4:28 ` Mark H Weaver
2016-08-11 5:56 ` Mike Miller
2016-08-11 9:58 ` Mark H Weaver
2016-08-10 4:23 ` Mark H Weaver
2016-08-10 6:43 ` Alex Vong
2016-08-11 6:26 ` Mike Miller
2016-08-11 15:27 ` Alex Vong
2016-08-11 17:04 ` Kei Kebreau
2016-08-13 12:37 ` Alex Vong
2016-08-12 11:45 ` JIT compiling Jordi Gutiérrez Hermoso
2016-08-12 15:08 ` Sergei Steshenko
2016-08-12 16:06 ` Oliver Heimlich
2016-08-13 1:03 ` Sergei Steshenko
2016-08-13 11:48 ` Alex Vong
2016-08-13 12:12 ` Alex Vong
2016-08-14 8:07 ` Sergei Steshenko
2016-08-14 10:21 ` Francesco Potortì
2016-08-14 20:20 ` Jordi Gutiérrez Hermoso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87popnjvaj.fsf@gnu.org \
--to=mthl@gnu.org \
--cc=alexvong1995@gmail.com \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.