ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: Mikhail Efremov <sem@altlinux.org>
To: devel@lists.altlinux.org
Subject: Re: [devel] [Legal] Лицензия у ClamAV
Date: Fri, 11 Mar 2016 17:31:11 +0300
Message-ID: <20160311173111.569867cc@sem.office.altlinux.ru> (raw)
In-Reply-To: <201603111713.32120.asy@altlinux.ru>

On Fri, 11 Mar 2016 17:13:32 +0400 Sergey Afonin wrote:
> Приветствую.
> 
> legal@lists, похоже, так и не пользуется популярностью, потому сюда.
> Что-то заглянул вчера в дерево исходников ClamAV на предмет, какая
> там лицензия, и несколько удивился. Кроме GPL/LGPL (причём первая v2,
> вторая v2.1), там лежит целый выводок BSD-подобных, есть Apache и одна
> проприетарная (unrar):

/usr/share/doc/rpm-build-licenses-2.0.5/README:

Questions & Answers:
Q1: What if a package contains parts under different licenses?
A: Consider splitting the package into subpackages. If it is not
feasible for some reason, mention both licenses, separating them with a
comma, e.g.: %gpl2plus, %lgpl2plus

Q2: What if a package can be distributed under several licenses?
A: Mention the applicable licenses, separating them with a pipe sign or 'or'
word (NOT with a slash), e.g.:
%mpl|%gpl2plus|lgpl2plus (Firefox license)
%gpl2plus or %artistic_license (Perl license; better use %perl_license)

Q3: Why shouldn't I use a slash to separate licenses?
A: Because of an ambiguity. Consider "GPL/LGPL v.2" that usually means
"GPLv2+, LGPLv2+" (as in FAQ1) and "GPL/Artistic" (Perl license that means
"Either GPL or Artistic". The initial proposal was here:
http://lists.altlinux.org/pipermail/devel/2007-August/049382.html (in
Russian).

-- 
WBR, Mikhail Efremov


  reply	other threads:[~2016-03-11 14:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-11 13:13 Sergey Afonin
2016-03-11 14:31 ` Mikhail Efremov [this message]
2016-03-11 15:33   ` Sergey Y. Afonin

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=20160311173111.569867cc@sem.office.altlinux.ru \
    --to=sem@altlinux.org \
    --cc=devel@lists.altlinux.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

ALT Linux Team development discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
		devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
	public-inbox-index devel

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git