Felipe Sateler | 1 Dec 2011 04:13
Picon
Favicon

Re: ignoring autotool in debian/copyright?

On Wed, Nov 30, 2011 at 00:16, Jonas Smedegaard <dr <at> jones.dk> wrote:
> On 11-11-21 at 11:25am, IOhannes m zmoelnig wrote:
>> On 2011-11-21 03:26, Felipe Sateler wrote:
>> > Looks like there is a strange thing with the install-sh section in
>> > debian/copyright. The license name contains spaces, and doesn't
>> > match any License: paragraph.
>
> I guess what you find strange is license names of this form:
>
> License: GPL-2+ with Libtool exception
>
> That, I believe, is perfectly correct according to (latest drafts of)
> DEP-5.  Please elaborate what you find strange about it.

I do not know what is the current status of DEP5. What I found strange
was the use of spaces (which are otherwise used as separator) in the
license name.

>
>
>> > I'm not quite sure what is the dep5 way to deal with this. Most
>> > likely the exception should be moved into the license paragraph and
>> > the qualificators to the name (with X exception) removed.
>
> Yes, treating a license that contains an exception as a combined unique
> license is also allowed by DEP-5, but is less usable, as the underlying
> general license is then not machine-readable.
>
>
>> it seems that all those problems only come from the autotools
(Continue reading)

Reinhard Tartler | 1 Dec 2011 08:20
Picon

Re: ignoring autotool in debian/copyright?

On Do, Dez 01, 2011 at 04:13:35 (CET), Felipe Sateler wrote:

> On Wed, Nov 30, 2011 at 00:16, Jonas Smedegaard <dr <at> jones.dk> wrote:
>> On 11-11-21 at 11:25am, IOhannes m zmoelnig wrote:
>>> On 2011-11-21 03:26, Felipe Sateler wrote:
>>> > Looks like there is a strange thing with the install-sh section in
>>> > debian/copyright. The license name contains spaces, and doesn't
>>> > match any License: paragraph.
>>
>> I guess what you find strange is license names of this form:
>>
>> License: GPL-2+ with Libtool exception
>>
>> That, I believe, is perfectly correct according to (latest drafts of)
>> DEP-5.  Please elaborate what you find strange about it.
>
> I do not know what is the current status of DEP5. What I found strange
> was the use of spaces (which are otherwise used as separator) in the
> license name.
>
>>
>>
>>> > I'm not quite sure what is the dep5 way to deal with this. Most
>>> > likely the exception should be moved into the license paragraph and
>>> > the qualificators to the name (with X exception) removed.
>>
>> Yes, treating a license that contains an exception as a combined unique
>> license is also allowed by DEP-5, but is less usable, as the underlying
>> general license is then not machine-readable.
>>
(Continue reading)

Fabian Greffrath | 1 Dec 2011 09:57
Favicon

Re: ignoring autotool in debian/copyright?

Am 01.12.2011 08:20, schrieb Reinhard Tartler:
> Thank you very much for stating your opinion such clearly. I fully
> concur with your view on DEP-5!

While I also agree with your opinion with regard to documenting the 
licensing of auto-generated files (and most parts of the GNU auto* 
build system, FWIW) I have to disagree with your statement that code 
which does not end up in binaries does not have to get documented in 
debian/copyright.

In my understanding, said file is to document the license and 
copyright situation of the packages that Debian offers - but Debian 
does also offer the source package, it is not limited to binary 
packages! If your source ships a convenience copy of a library which 
you do not link against - which you maybe do not even compile, because 
you build against the system library - then of course the license of 
this code has to end up in debian/copyright.

  - Fabian
Reinhard Tartler | 1 Dec 2011 10:18
Picon

Re: ignoring autotool in debian/copyright?

On Do, Dez 01, 2011 at 09:57:44 (CET), Fabian Greffrath wrote:

> Am 01.12.2011 08:20, schrieb Reinhard Tartler:
>> Thank you very much for stating your opinion such clearly. I fully
>> concur with your view on DEP-5!
>
> While I also agree with your opinion with regard to documenting the
> licensing of auto-generated files (and most parts of the GNU auto* build
> system, FWIW) I have to disagree with your statement that code which
> does not end up in binaries does not have to get documented in
> debian/copyright.
>
> In my understanding, said file is to document the license and copyright
> situation of the packages that Debian offers - but Debian does also
> offer the source package, it is not limited to binary packages! If your
> source ships a convenience copy of a library which you do not link
> against - which you maybe do not even compile, because you build against
> the system library - then of course the license of this code has to end
> up in debian/copyright.

I hear this opinion at many places, but it does not match my
understanding of Debian Policy (cf. sections §2.3, §12.5). The very
first sentence reads like this:

,----[ Debian Policy §2.3 / §12.5
| Every package must be accompanied by a verbatim copy of its copyright
| information and distribution license in the file
| /usr/share/doc/package/copyright. This file must neither be compressed
| nor be a symbolic link.
`----
(Continue reading)

Fabian Greffrath | 1 Dec 2011 10:30
Favicon

Re: ignoring autotool in debian/copyright?

Am 01.12.2011 10:18, schrieb Reinhard Tartler:
> And thinking more about it, source packages do already have proper
> copyright information in the source package, mostly in some COPYING or
> README file or in the respective sources. So legally, there is no
> necessity to collect and condense all this information in a single file
> "debian/copyright". Doing so may be a great service for people that work
> on the source packages, right, but I really don't think this is
> currently a requirement, nor should maintainers be forced to do so.

Hm, valid point. I don't believed this has not been discussed on a 
grand scale before and didn't lead to a consensus. The topic is just 
too important.
IOhannes m zmoelnig | 1 Dec 2011 11:26
Picon

Re: ignoring autotool in debian/copyright?


On 2011-11-30 04:16, Jonas Smedegaard wrote:
> You can (with your Debian hat on, I am not talking about upstream here) 
> repackage the source to *not* include the autogenerated files as part of 
> Debian distributed sources.  IF the files truly are only autogenerated 
> at the target build host you need not document it - but all that we ship 

mind that i "somewhat" agree with that (i call it "somewhat" because i
can see and appreciate the value of having everything in the source
package being documented, while at the same time i'm still lazy and
would happily not do it if this is not only tolerated by accepted
behaviour),

the reason why i started this discussion is not because i don't care
about licensing of those files; but that i think - as felipe has already
pointed out - that "properly" documenting those files as is currently
suggested only creates noise.

my reasoning is, that those generated (but copyrighted) files, are
virtually the same for all packages that use autotools.
assuming that about 40%  of all the C/C++ based debian packages use
autotools  (that is just a wild guess based on nothing but intuition)
this would eventually suggest that we add the very same information to
about 4000 packages or so (naively interpolating from debtags)

i thought that it might be helpful, if we shorten that information to
something like
<snip>
Files: libtool, config.sub, config.guess,...
License: autotools
(Continue reading)

CONSULATE HAFEEZ EL-BADRY | 1 Dec 2011 12:52
Picon

REQUEST FOR YOUR PARTNERSHIP

Hello,

We are brokering an Investment deal in your country on behalf of a client
in Libya. This deal will involve the investment of a high profile client of
ours in your country. We are by this letter offering you our partnership,
so as to allow us have you as representative and manager of invested funds
in your country within the time frame of the investment/partnership scheme.

Please reply via email: conslate.afeez <at> hotmail.com for an elaborate
proposal and details of the offer.

Yours sincerely,
Hafeez El-Badri
LIBYA CONSULATE
Picasa Web Album | 1 Dec 2011 19:20
Picon
Favicon

Nuova attività di Picasa Web Album

Caricamenti recenti
Alessio Treglia ha aggiunto 5 foto a UDS-P
30-nov-2011 10.16.28

Pubblica commento Annulla l'iscrizione a questo utente.
_______________________________________________
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers <at> lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Jonas Smedegaard | 1 Dec 2011 19:25
X-Face
Face
Picon
Gravatar

Re: ignoring autotool in debian/copyright?

On 11-12-01 at 11:26am, IOhannes m zmoelnig wrote:
> the reason why i started this discussion is not because i don't care 
> about licensing of those files; but that i think - as felipe has 
> already pointed out - that "properly" documenting those files as is 
> currently suggested only creates noise.
> 
> my reasoning is, that those generated (but copyrighted) files, are 
> virtually the same for all packages that use autotools.
> assuming that about 40% of all the C/C++ based debian packages use 
> autotools (that is just a wild guess based on nothing but intuition) 
> this would eventually suggest that we add the very same information to 
> about 4000 packages or so (naively interpolating from debtags)

If code is duplicated 4000 times, then licensing of code needs to be 
stated 4000 times.

> i thought that it might be helpful, if we shorten that information to 
> something like
> <snip>
> Files: libtool, config.sub, config.guess,...
> License: autotools
>   see /usr/share/doc/licenses/autotools
> </snip>
> 
> i'm aware that it might not be that simple, as i haven't followed the 
> evaluation of the various licenses applied to autotools generated 
> files.

Feel free to file a bug report against base-files.

I doubt it will be accepted, because it is not a single license but a 
range of different licenses carefully applied to various of the 
autogenerated files.

> > If you are lazy and want least possible documentation of autotools, 
> > then add a single Files section something like this:
> > 
> > Files: configure*
> >  Makefile*
> >  *m4*
> >  config*
> >  libtool*
> > Copyright: 1992-2008, Free Software Foundation, Inc.
> > License: GPL-2+
> > 
> > Extend with "missing, depcomp, etc" and don't give a shit about 
> > exceptions or more liberal licensing - just treat it all as being 
> > contaminated with GPL-2+.
> 
> which is a similar suggestion as mine above.
> however, i'm not so convinced about the "contaminated with GPL-2+" 
> argument.

Treating them all as GPL-2+ is the very essence of the proposal: Avoids 
changing base-files.

> > I sure prefer if you are not lazy but instead respectful to those 
> > developers that put effort into inventing and maintaining a tool 
> > that is clearly good enough that you use it.
> 
> hmm, i don't think this is about not respecting the developers of 
> those great tools. even if i was "lazy and [...] treat it all as [...] 
> GPL-2+" there would be a copyright clause that acknowledges the work.

Respecting copyright is one thing. Respecting licensing is another.

> and with my debian hat on, it was not my decision to use those tools; 
> i only respect upstreams intention.

You have the option of repackaging the source with those autogenerated 
files removed.

 - Jonas

--

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private
_______________________________________________
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers <at> lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Jonas Smedegaard | 1 Dec 2011 19:46
X-Face
Face
Picon
Gravatar

Re: ignoring autotool in debian/copyright?

On 11-12-01 at 12:13am, Felipe Sateler wrote:
> On Wed, Nov 30, 2011 at 00:16, Jonas Smedegaard <dr <at> jones.dk> wrote:
> > On 11-11-21 at 11:25am, IOhannes m zmoelnig wrote:
> >> On 2011-11-21 03:26, Felipe Sateler wrote:
> >> > Looks like there is a strange thing with the install-sh section 
> >> > in debian/copyright. The license name contains spaces, and 
> >> > doesn't match any License: paragraph.
> >
> > I guess what you find strange is license names of this form:
> >
> > License: GPL-2+ with Libtool exception
> >
> > That, I believe, is perfectly correct according to (latest drafts 
> > of) DEP-5.  Please elaborate what you find strange about it.
> 
> I do not know what is the current status of DEP5. What I found strange 
> was the use of spaces (which are otherwise used as separator) in the 
> license name.

If you mean the spaces in above example, then it is IMO pretty clearly 
documented at http://dep.debian.net/deps/dep5/#license-specification

 - Jonas

--

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private
_______________________________________________
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers <at> lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Gmane