devel@ where you _can_ ask
 help / color / mirror / Atom feed
From: Mikhail Efremov <sem@altlinux.org>
To: devel-newbies@lists.altlinux.org
Subject: Re: [newbies] Как правильно указать смешанную лицензию в спеке?
Date: Tue, 26 Jan 2016 14:19:01 +0300
Message-ID: <20160126141902.0ed7b78a@sem-notebook> (raw)
In-Reply-To: <56A71707.70601@ya.ru>

On Tue, 26 Jan 2016 13:49:43 +0700 Антон Мидюков wrote:
> Как будет выглядеть строка license в спеке, если нужно указать 
> одновременно GPL-3.0 и Apache-2.0?

/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


      parent reply	other threads:[~2016-01-26 11:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-26  6:49 Антон Мидюков
2016-01-26 11:03 ` Stas
2016-01-26 11:19 ` Mikhail Efremov [this message]

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=20160126141902.0ed7b78a@sem-notebook \
    --to=sem@altlinux.org \
    --cc=devel-newbies@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

devel@ where you _can_ ask

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/devel-newbies/0 devel-newbies/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-newbies devel-newbies/ http://lore.altlinux.org/devel-newbies \
		devel-newbies@lists.altlinux.org devel-newbies@lists.altlinux.ru devel-newbies@lists.altlinux.com
	public-inbox-index devel-newbies

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


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