From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Enge Subject: Re: [PATCH] gnu: Add psutils. Date: Wed, 23 Jan 2013 21:07:44 +0100 Message-ID: <201301232107.44760.andreas@enge.fr> References: <201301202333.31367.andreas@enge.fr> <201301212145.56116.andreas@enge.fr> <87sj5u5f8l.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="Boundary-01=_QMEARGt26rlhx4A" Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:43408) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ty6c6-0004xH-2g for bug-guix@gnu.org; Wed, 23 Jan 2013 15:08:05 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ty6c0-0002Tq-5w for bug-guix@gnu.org; Wed, 23 Jan 2013 15:08:01 -0500 In-Reply-To: <87sj5u5f8l.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=_QMEARGt26rlhx4A Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Am Montag, 21. Januar 2013 schrieb Ludovic Court=C3=A8s: > Andreas Enge skribis: > > Is this not exactly how bsd-style operates? > Yes, but it=E2=80=99s only for BSD-style licenses. =46inally I think we agree. I was suggesting to create something analogous = to=20 bsd-style, just with a different name. But maybe bsd-style is enough, as=20 the description is sufficiently vague: "This is a BSD-style, non-copyleft free software license." =46ontconfig poses the same problem: They use something that looks=20 essentially like the MIT/X11 license, but with a slightly different=20 wording. So shall we create a new category, and if yes, under which name? Or shall=20 we use "bsd-style" for anything that does not fit? Andreas --Boundary-01=_QMEARGt26rlhx4A Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

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

> Andrea= s Enge <andreas@enge.fr> skribis:

> > I= s this not exactly how bsd-style operates?

> Yes, b= ut it=E2=80=99s only for BSD-style licenses.

&nb= sp;

Finally I t= hink we agree. I was suggesting to create something analogous to bsd-style,= just with a different name. But maybe bsd-style is enough, as the descript= ion is sufficiently vague:

"This = is a BSD-style, non-copyleft free software license."

&nb= sp;

Fontconfig = poses the same problem: They use something that looks essentially like the = MIT/X11 license, but with a slightly different wording.

&nb= sp;

So shall we= create a new category, and if yes, under which name? Or shall we use "= ;bsd-style" for anything that does not fit?

&nb= sp;

Andreas

&nb= sp;

--Boundary-01=_QMEARGt26rlhx4A--