From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Enge Subject: Re: [PATCH] gnu: Add psutils. Date: Mon, 21 Jan 2013 21:45:55 +0100 Message-ID: <201301212145.56116.andreas@enge.fr> References: <201301202333.31367.andreas@enge.fr> <87wqv68f8n.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="Boundary-01=_Dka/QK3U+rXqnjQ" Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:35708) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TxOFv-0002Gc-QT for bug-guix@gnu.org; Mon, 21 Jan 2013 15:46:14 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TxOFo-0002ui-L9 for bug-guix@gnu.org; Mon, 21 Jan 2013 15:46:11 -0500 In-Reply-To: <87wqv68f8n.fsf@gnu.org> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: Ludovic =?utf-8?q?Court=C3=A8s?= Cc: bug-guix@gnu.org --Boundary-01=_Dka/QK3U+rXqnjQ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Am Montag, 21. Januar 2013 schrieb Ludovic Court=C3=A8s: > > Does it qualify as "bsd-like"? > It looks like BSD-3 to me, or at least =E2=80=9CBSD-like=E2=80=9D. Sort of. Except that the second clause states that source code needs to be= =20 provided, whereas BSD just states that binary distributions need to keep=20 the copyright notice. I could also add an entry to the licenses file, but I am afraid we might=20 end up with almost as many licenses as packages. > > If not, would it make sense to add a license "other" to licenses.scm, > > which takes the same parameters as "bsd-like"? > I think (guix licenses) should export the constructor, but under the > name =E2=80=98make-license=E2=80=99 to avoid clashes with the =E2=80=98li= cense=E2=80=99 field in > =E2=80=98package=E2=80=99 records. Is this not exactly how bsd-style operates? > Please align the opening paren under the =E2=80=98u=E2=80=99. > Please put the comment above the line it refers to, and move closing > parentheses to the end of the line. Okay, no problem. Andreas --Boundary-01=_Dka/QK3U+rXqnjQ Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

Am Montag, = 21. Januar 2013 schrieb Ludovic Court=C3=A8s:

> > D= oes it qualify as "bsd-like"?

> It loo= ks like BSD-3 to me, or at least =E2=80=9CBSD-like=E2=80=9D.

&nb= sp;

Sort of. Ex= cept that the second clause states that source code needs to be provided, w= hereas BSD just states that binary distributions need to keep the copyright= notice.

&nb= sp;

I could als= o add an entry to the licenses file, but I am afraid we might end up with a= lmost as many licenses as packages.

&nb= sp;

> > I= f not, would it make sense to add a license "other" to licenses.s= cm,

> > w= hich takes the same parameters as "bsd-like"?

> I thin= k (guix licenses) should export the constructor, but under the

> name = =E2=80=98make-license=E2=80=99 to avoid clashes with the =E2=80=98license= =E2=80=99 field in

> =E2=80= =98package=E2=80=99 records.

&nb= sp;

Is this not= exactly how bsd-style operates?

&nb= sp;

> Please= align the opening paren under the =E2=80=98u=E2=80=99.

> Please= put the comment above the line it refers to, and move closing

> parent= heses to the end of the line.

&nb= sp;

Okay, no pr= oblem.

&nb= sp;

Andreas

&nb= sp;

--Boundary-01=_Dka/QK3U+rXqnjQ--