Re: Newbie Help - Ruby on Rails packaging questions.
After spending a bit of time with "licensecheck" and a some command
line friends I now have a debian/copyright file that conforms to the
proposed CopyrightFormat. The problem is that weighing in @ 388
lines, it is huge! It turns out that while most of the files in
redmine are GPL they have a bunch of different Copyright notices,
usually just differing by year.
Should I just combine the similar (same person) copyrights into a
single one covering all the years or am I supposed to list each one
separately? Also, there are quite a few files that have no copyright
or license info at all. Things like db/migrate scripts, sample code,
and examples. Since they are not explicably licensed/copyrighted does
that mean that they fall under the project license/copyright?
On Jul 21, 2008, at 9:37 AM| Jul 21, 2008, Jan Beyer wrote:
On 07/21/2008 03:20 PM, Richard Hurt wrote :
You'll have to have all this information in the copyright file. If
have a look at http://wiki.debian.org/Proposals/CopyrightFormat on
OK, I am attempting to package up redmine and need some general
pointers. I'm going through the New Maintainers Guide tutorial and
run into a few things that I need clarification on.
1) Is there any type of automated way to extract license info from a
series of files? I am using a simple grep to do my heavy lifting
seems pretty crude; has no one built anything better?
2) redmine itself is under GPL-2 but there are some files in the
under various other license (MIT, LGPL, Ruby) and some files have no
license at all. How do I represent this information in the
debian/copyright file? Listing each file and it's license
would be overwhelming. What is the best practice here?
could format this information. Usually, there are only finitely many
different combinations of copyright/license, to which you can list the
corresponding files, possibly using wildcards like *,? ...
Good luck! ;-)
To UNSUBSCRIBE, email to debian-mentors-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org