www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shane Curcuru (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LEGAL-316) Use of struct definitions and #defines from LGPL source
Date Tue, 18 Jul 2017 12:05:01 GMT

    [ https://issues.apache.org/jira/browse/LEGAL-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091466#comment-16091466
] 

Shane Curcuru commented on LEGAL-316:
-------------------------------------

Can we please be specific as to 1) what, exactly we're planning, and 2) why this is not a
slippery slope?   There are several different details in the conversation here, so we need
to be clear when we arrive at an answer (and presumably post it as a FAQ for this specific
case).

This, it would help if [~tlipcon] could provide a detailed description of what actual data
or files are planned to be included.

Separately, as an unofficial concept, I could imagine including an entire, unmodified LGPL
header.h file in an ASF source control and corresponding release that pointed to obvious and
widely-used system dependencies that the common user of that ASF product would typically already
have installed.  That would require a careful description of the inclusion in the NOTICE or
some similar place to ensure that users aren't surprised, and with a statement as to why the
release as a whole is otherwise under the AL or similar.

I'm having a hard time imagining any other cases involving *GPL licensed files in ASF source
control.  But we need the specific details of use to decide the right answer.


> Use of struct definitions and #defines from LGPL source
> -------------------------------------------------------
>
>                 Key: LEGAL-316
>                 URL: https://issues.apache.org/jira/browse/LEGAL-316
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Todd Lipcon
>
> In Kudu, we are looking to make use of an XFS-specific ioctl() which requires a specific
struct xfs_flock64 to be passed as its argument. The struct is not available in commonly-distributed
headers but is part of the public API of XFS, and defined in the Linux source tree in an [LGPL-licensed
header|https://github.com/torvalds/linux/blob/fe7a719b30dfdb4d55680461954b99b257ebe671/fs/xfs/libxfs/xfs_fs.h#L126].
We also need the definition of XFS_IOC_UNRESVSP64 defined [here|https://github.com/torvalds/linux/blob/fe7a719b30dfdb4d55680461954b99b257ebe671/fs/xfs/libxfs/xfs_fs.h#L509].
> Since the file isn't commonly installed by default, we would like to copy-paste the struct
definition and define into our own code. According to Richard Stallman on http://lkml.iu.edu/hypermail/linux/kernel/0301.1/0362.html:
> {quote}
>  Our view is that just using structure 
> definitions, typedefs, enumeration constants, macros with simple 
> bodies, etc., is NOT enough to make a derivative work
> {quote}
> Additionally, Google has been extracting struct definitions from Linux and redistributing
them as part of their BSD-licensed bionic library for the past 6 years on Android. So, we
believe there is precedent and this should be fine for us. Just looking for confirmation from
ASF Legal.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


Mime
View raw message