Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 174464 - net-misc/iputils: missing LGPL-2 from LICENSE
Summary: net-misc/iputils: missing LGPL-2 from LICENSE
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-13 14:16 UTC by Daniel Drake (RETIRED)
Modified: 2007-04-13 15:54 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Drake (RETIRED) gentoo-dev 2007-04-13 14:16:16 UTC
The iputils source tarball includes duplicated headers from glibc, such as socketbits.h, under the include-glibc directory. Please make the LICENSE variable reflect this.
Comment 1 Daniel Drake (RETIRED) gentoo-dev 2007-04-13 14:29:20 UTC
To add to the mix:

It also includes GPL-2 code (iputils/Modules/pg3.c), and a Sun license similar to as-is (rdisc.c).
Comment 2 SpanKY gentoo-dev 2007-04-13 14:45:51 UTC
looks like you're looking at an older version ... plus, i'm not really sure about that ... header usage does not mean your source is under the LGPL-2

pg3.c is a linux kernel module which isnt built/installed as part of the ebuild, so GPL-2 isnt appropriate either
Comment 3 Daniel Drake (RETIRED) gentoo-dev 2007-04-13 15:29:12 UTC
I agree, the LGPL explicitly states that header usage doesn't bind your program to  the LGPL.

However, I thought the ebuild LICENSE field was supposed to indicate the license acceptance required for source redistribution. Am I wrong?
Comment 4 SpanKY gentoo-dev 2007-04-13 15:54:01 UTC
i dont believe so ... i think the interpretation is more what you'll actually be utilizing once the package has been merged ...

otherwise, it'd be impossible to emerge a package that has optional proprietary components based on USE flags ...

i believe Debian also takes this view point (license reflects installed state)