On Friday 28 November 2003 01:19, Luke-Jr wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Thursday 27 November 2003 04:12 pm, Jason Wever wrote:
> > My $0.02 is that if this gets implemented, it should be put in so that
> > the default behavior is like portage is now,
>
> Since Portage as it is right now doesn't pay any attention to licenses, its
> legality could be questioned (as with the games issue before?)

My main concern from this perspective is whether "*" should be available at 
all.

> > and if you choose to restrict
> > yourself to only free software or other licensing scheme, you can make
> > the necessary changes yourself.  Otherwise you will have a ton of users
> > asking "why can't i emerge package foo?", or filing bugs because of this,
> > etc.
>
> If Portage displays a clear enough message, there shouldn't be a problem
> with this...

This shouldn't be a problem as long as users get a *loud* advance warning. Not 
only should it be in pkg_postinst but maybe also in the GWN?

> From a support perspective, if this gets implemented, I'm forwarding all
>
> > of these questions, bugs, etc to the "free and only free" software folks.
> > Please dont' take away one "freedom" for another.
>
> As long as there is an option (editing the ACCEPT_LICENSES), there is no
> freedom being removed.

I think the osf/fsf licenses are the best default. From what I've seen working 
on a licensing patch, most of the base system is covered by a handful of 
licenses. I have 352 packages installed on my system and my ACCEPT_LICENCE is 
as follows:
ACCEPT_LICENSE="Artistic MIT ZLIB BZIP2 FLEX CRACKLIB LGPL-2 NVIDIA LGPL-2.1
BSD fontconfig Info-ZIP X11 MSttfEULA PSF-2.2 freedist BAEKMUK Arphic
free-noncomm sun-bcla-java-vm DB IPL-1 DIVX MOTIF XAnim public-domain FDL-1.1
wxWinLL-3 OpenSoftware as-is GPL-2"

There's 31 licenses there. Installing all of gnome only requires PYTHON for 
pyxml MPL-1.1 and NPL-1.1 for mozilla and Ximian-logos for bug-buddy. I 
haven't looked into the licenses themselves so I don't know what would be 
"free" and "non-free" but it's definately not the maintenance nightmare 
people are worried about.

Regards,
Jason Stubbs


--
[EMAIL PROTECTED] mailing list

Reply via email to