Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 425930 - dev-libs/cyrus-sasl's LICENSE variable does not reflect init script
Summary: dev-libs/cyrus-sasl's LICENSE variable does not reflect init script
Status: CONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal QA
Assignee: No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: init-script-license
  Show dependency tree
 
Reported: 2012-07-11 17:17 UTC by Ian Stakenvicius (RETIRED)
Modified: 2022-02-23 02:29 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ian Stakenvicius (RETIRED) gentoo-dev 2012-07-11 17:17:44 UTC 
The init script(s) provided in FILESDIR for dev-libs/cyrus-sasl has a license of GPL-2 but GPL-2 isn't within the LICENSE variable of the ebuild(s):

files/pwcheck.rc6 has license line:
# Distributed under the terms of the GNU General Public License v2
... and is used by the following ebuilds:
cyrus-sasl-2.1.23-r6.ebuild:LICENSE="as-is"
cyrus-sasl-2.1.25.ebuild:LICENSE="as-is"
cyrus-sasl-2.1.25-r1.ebuild:LICENSE="as-is"
cyrus-sasl-2.1.25-r2.ebuild:LICENSE="as-is"

files/saslauthd2.rc6 has license line:
# Distributed under the terms of the GNU General Public License v2
... and is used by the following ebuilds:
cyrus-sasl-2.1.23-r6.ebuild:LICENSE="as-is"
cyrus-sasl-2.1.25.ebuild:LICENSE="as-is"
cyrus-sasl-2.1.25-r1.ebuild:LICENSE="as-is"
cyrus-sasl-2.1.25-r2.ebuild:LICENSE="as-is"

There are two options here -- either LICENSE in the ebuilds should be appended with GPL-2 to cover the init script, or the init script should be relicensed so that it is covered by current LICENSE (this one is probably the preferred resolution).  See also bug 425702 .