Re: NOTE: Please publicize any license changes to your packages

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 2007-07-24 at 13:55 -0700, Arjan van de Ven wrote:
> On Tue, 2007-07-24 at 12:51 -0800, Jeff Spaleta wrote:
> 
> >  I'd really like to avoid a situation where we have to start
> > arbitrarily rolling back commits to clean up linking violations which
> > could have been avoided through reasonable communication.  As more
> > individual projects who were previous under LGPL2/GPL2 start
> > relicensing we may need to adjust how we do things until the licensing
> > situation settles out and upstream projects are back to a consistent
> > understood licensing state.
> 
> this is where tools help!
> if the License: tag is machine parsable, at least some of the "mistakes"
> can be detected. It won't be perfect, but it's at least some level of
> safeguard.

We should be *reducing* the amount of manually-created goo[1] involved
in putting software into Fedora, not increasing it.

An automatic tool which scans the actual sources included upstream
wouldn't be difficult to write.  In fact it seems very likely to already
exist, though I couldn't find something in a quick search.

Automating the checking would also allow us to catch changes
automatically.  


-- 
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux