Date: Wed, 5 Mar 2008 11:30:44 -0500 From: Wesley Shields <wxs@FreeBSD.org> To: freebsd-ports@freebsd.org Subject: Re: interactive ports - the plague Message-ID: <20080305163044.GA82442@atarininja.org> In-Reply-To: <20080305162228.3dedeab3@anthesphoria.net> References: <47CBC3C5.9050007@bsdforen.de> <20080303155354.2043d131@gumby.homeunix.com.> <47CC26F3.7020709@cyberbotx.com> <15808613.post@talk.nabble.com> <20080303195704.GA18100@soaustin.net> <56a0a2840803041035n3f6b30davc1f97d9333c817a8@mail.gmail.com> <20080305162228.3dedeab3@anthesphoria.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 05, 2008 at 04:22:28PM +0100, Nikola Le??i?? wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: RIPEMD160 > > On Tue, 4 Mar 2008 19:35:29 +0100 > "Jesper Louis Andersen" <jesper.louis.andersen@gmail.com> wrote: > > > I am not sure it would solve the particular problem, but one could > > take a look at how NetBSDs pkgsrc build system copes with licenses in > > general: > > > > For each license type, there is a knob. The knob could normally be > > interactive, yielding the exact same behaviour as now. But if an > > appropriate ACCEPT_LICENSE_FOO=Yes is found in make.conf, then the > > user has read and accepted that particular license type once and for > > all. > > The purpose of this pkgsrc's mechanism is to segregate pieces of > software that use various licences so that users have a better legal / > / philosophical control over what is installed on their systems. This > doesn't change anything if you have to go to the vendor's site, log in > and accept the licence manually. > > > The downside is that this requires a considerable amount of work and > > thought. What should happen when the license changes, for instance. > > Then port (or package, in pkgsrc terminology) maintainer changes the > appropriate line in package's Makefile. If the license in question is a > new one, its text is being added to the pkgsrc tree. > > (BTW, are/were there ideas of implementing something similar in Ports > Collection?) I know there is a wiki page keeping track of ports which use GPL3 (not sure why, I have not kept up on what GPL3 means). If the reason for having this page is important enough - that is, more than curiosity - then some kind of analogous mechanism to what you describe may be a good idea. -- WXS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080305163044.GA82442>