Re: DSFG Explanation for non-free packages?
On Mon, Jun 29, 1998 at 02:55:29AM -0500, Ted Whalen wrote:
> Idea: A file gets stuck in the /usr/doc/<package> of each non-free or
> contrib packages explaining exactly why the particular license of that
> package is in conflict with the DSFG.
>
> I'm just going to toss out an example, to get the ball rolling. Some
> standard verbiage could be hammered together later, by smarter people
> than me.
>
> /usr/doc/tin/dsfg-conflict:
>
> DSFG Guideline 1: Free Redistribution
I like this idea allot. This could perform a number of functions.
I for one never really pay attention to whether packages I install are
non-free, contrib, or main (and with the advent of apt-get, that distinction
is really getting blurred for me...I love apt-get :) )
Also, it would be nice to include the wording from the actual licence which
causes the problem (unless of course it is a lack of wording that
causes it). This could alleviat ethe "Why is this in non-free?" and also
make it much easier to look at and determine if the licecnes has changed
between versions (ie maybe it became free? ..dare to dream :) )
> --- snip ---
>
> I realize this message is pretty long, but I thought that this would be
> a good idea, both to educate people about what DSFG-free means, and
> about why some licenses are non-free. Also, these exlanatory files
> would make it easier for people to realize if they might perhaps be in
> violation of a license themselves. Just throwing it out for
> discussion.
as I said I like this idea....but...I think this is really important for
development libraries. I would hate to be writting a program and suddenly find
out that the library i was using was non-free..and have to go back and
choose a new library and fix it all.
-Steve
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: