Hi Mel, Eric, and Jarod, I'm looking into uploading libhugetlbfs to Debian, and I wanted to double-check a few files with ambiguous copyright or license notices. I assume they're all intended to be LGPLv2.1+ like the rest of the package but they're not labeled as such.
* huge_page_setup_helper.py is labeled just "(c) Red Hat, Inc., 2009," but does not have a license statement. Jarod, can this be used under LGPLv2.1+? * Similarly, oprofile_start.sh just says "oprofile_start.sh (c) Mel Gorman 2008" with no license statement. Mel, is this also LGPLv2.1+? * A few files (TLBC/*, contrib/tlbmiss_cost.sh, cpupcstat, oprofile_map_events.pl) are "Licensed under LGPL 2.1 as packaged with libhugetlbfs." Eric, Mel, I assume that these are intended to be LGPLv2.1 or any higher version, like the rest of the package? Less importantly: * alloc.c and two tests have _just_ a license, not a copyright statement; I guess they're owned by IBM? * There are a few other files without copyright notices, but right now I'm assuming they're under the LGPL (though it would be great to have comments on them, or a clear statement in a README). It's the ones that have a copyright statement and no license that I want to be particularly sure of. * For the files that say things like "Copyright (C) 2005-2006 David Gibson & Adam Litke, IBM Corporation.", do you know if the copyright is held by the individuals as well as IBM, or just by IBM? I can just copy these statements verbatim into debian/copyright, but it seems worth clarifying. Sorry about the annoyance, but Debian cares about getting this stuff right (and I think that's a good policy, honestly). I can send in a follow-up patch to add comments to the files that don't have copyright notices once I get responses; I'd also be okay with a notice in the README that clearly asserts a license for the entire package, if you'd prefer that. (By the way, I seem to be unable to subscribe to the librelist, which is maybe where I should ask this - at least I have gotten no confirmation email from my subscribe email, and I'm not sure how to send without first subscribing as described in SubmittingCode.) Also if there's anything you'd like me to be aware of when preparing the Debian package or to package in a certain way, do let me know. Thanks, -- Geoffrey Thomas geo...@hudson-trading.com
