> On Thu, Jun 30, 2005 at 10:28:56AM +0100, Phil Dillon-Thiselton wrote:
> > This is not so easy - too many people assume that the
> license issue is as
> > simple as GPL, LGPL, BSD but it's not - some applications
> have their very
> > own license
>
> Yea, we've thought about that. Currently, the winning idea
> is one where
> we provide a "licenses" package that includes all the standard F/OSS
> licenses out there. Then the PKGBUILD's license array can
> included one
> or more of these (some software is multi-licensed).
>
> If a piece of software has a custom license, then we could write
> something like "custom" in the license field and include the license
> itself in /usr/share/licenses/{pkgname}.
>
> Thoughts?
>
>
> - J
Don't forget: you might also need to include version numbers for the license.
GPL 3.0 is currently on the drawing board, and I imagine that whenever it comes
out there'll be a large amount of time where some apps will use the new one and
some apps will use the old. Ditto for other licenses.
DR
==============================================================================
Please access the attached hyperlink for an important electronic communications
disclaimer:
http://www.csfb.com/legal_terms/disclaimer_external_email.shtml
==============================================================================
_______________________________________________
arch mailing list
arch@archlinux.org
http://www.archlinux.org/mailman/listinfo/arch
