On Tue, 4 Oct 2016 14:15:28 +0200
Mathieu Arnold wrote:
> Le 04/10/2016 à 14:03, Montgomery-Smith, Stephen a écrit :
> > On 10/04/2016 06:47 AM, Mathieu Arnold wrote:
> >> Le 04/10/2016 à 09:29, Eitan Adler a écrit :
> >>> On 4 October 2016 at 00:25, Mathieu Arnold
> >>> wrote:
> Le 0
Le 04/10/2016 à 14:03, Montgomery-Smith, Stephen a écrit :
> On 10/04/2016 06:47 AM, Mathieu Arnold wrote:
>> Le 04/10/2016 à 09:29, Eitan Adler a écrit :
>>> On 4 October 2016 at 00:25, Mathieu Arnold wrote:
Le 04/10/2016 à 03:58, Montgomery-Smith, Stephen a écrit :
> Could we use USES=m
On 10/04/2016 06:47 AM, Mathieu Arnold wrote:
> Le 04/10/2016 à 09:29, Eitan Adler a écrit :
>> On 4 October 2016 at 00:25, Mathieu Arnold wrote:
>>> Le 04/10/2016 à 03:58, Montgomery-Smith, Stephen a écrit :
Could we use USES=metaport to suppress these messages?
>>> Suppress what messages ?
Le 04/10/2016 à 09:29, Eitan Adler a écrit :
> On 4 October 2016 at 00:25, Mathieu Arnold wrote:
>> Le 04/10/2016 à 03:58, Montgomery-Smith, Stephen a écrit :
>>> On 10/03/2016 07:34 AM, Eitan Adler wrote:
On 3 October 2016 at 05:31, Montgomery-Smith, Stephen
wrote:
> On 10/02/2016
On 4 October 2016 at 00:25, Mathieu Arnold wrote:
> Le 04/10/2016 à 03:58, Montgomery-Smith, Stephen a écrit :
>> On 10/03/2016 07:34 AM, Eitan Adler wrote:
>>> On 3 October 2016 at 05:31, Montgomery-Smith, Stephen
>>> wrote:
On 10/02/2016 05:27 PM, Eitan Adler wrote:
> On 2 October 2016
Le 04/10/2016 à 03:58, Montgomery-Smith, Stephen a écrit :
> On 10/03/2016 07:34 AM, Eitan Adler wrote:
>> On 3 October 2016 at 05:31, Montgomery-Smith, Stephen
>> wrote:
>>> On 10/02/2016 05:27 PM, Eitan Adler wrote:
On 2 October 2016 at 14:44, Montgomery-Smith, Stephen
wrote:
> So
On 10/03/2016 07:34 AM, Eitan Adler wrote:
> On 3 October 2016 at 05:31, Montgomery-Smith, Stephen
> wrote:
>> On 10/02/2016 05:27 PM, Eitan Adler wrote:
>>> On 2 October 2016 at 14:44, Montgomery-Smith, Stephen
>>> wrote:
So I have a couple of ports, science/cdf and graphics/opendx, which h
Le 03/10/2016 à 14:31, Montgomery-Smith, Stephen a écrit :
> On 10/02/2016 05:27 PM, Eitan Adler wrote:
>> On 2 October 2016 at 14:44, Montgomery-Smith, Stephen
>> wrote:
>>> So I have a couple of ports, science/cdf and graphics/opendx, which have
>>> licenses I can't find in Mk/bsd.licenses.db.mk
On 3 October 2016 at 05:31, Montgomery-Smith, Stephen
wrote:
> On 10/02/2016 05:27 PM, Eitan Adler wrote:
>> On 2 October 2016 at 14:44, Montgomery-Smith, Stephen
>> wrote:
>>> So I have a couple of ports, science/cdf and graphics/opendx, which have
>>> licenses I can't find in Mk/bsd.licenses.db
On 10/02/2016 05:27 PM, Eitan Adler wrote:
> On 2 October 2016 at 14:44, Montgomery-Smith, Stephen
> wrote:
>> So I have a couple of ports, science/cdf and graphics/opendx, which have
>> licenses I can't find in Mk/bsd.licenses.db.mk. How do I set LICENSE in
>> those ports?
>
> The other answers
On 2 October 2016 at 14:44, Montgomery-Smith, Stephen
wrote:
> So I have a couple of ports, science/cdf and graphics/opendx, which have
> licenses I can't find in Mk/bsd.licenses.db.mk. How do I set LICENSE in
> those ports?
The other answers are correct. If the license is standard (listed
here:
On Sun, 2 Oct 2016 18:44:43 +
"Montgomery-Smith, Stephen" wrote:
> So I have a couple of ports, science/cdf and graphics/opendx, which
> have licenses I can't find in Mk/bsd.licenses.db.mk. How do I set
> LICENSE in those ports?
Like this example:
LICENSE=CPLV1
LICENSE_NAME= CPL
On Sun, Oct 2, 2016 at 11:44 AM, Montgomery-Smith, Stephen <
step...@missouri.edu> wrote:
> So I have a couple of ports, science/cdf and graphics/opendx, which have
> licenses I can't find in Mk/bsd.licenses.db.mk. How do I set LICENSE in
> those ports?
>
> An even tougher one is math/octave-forg
Hi,
On Jun 15, 2010, at 01:10, Doug Barton wrote:
> My vote would be that we add a "PERL" category, but maybe there is a reason
> not to do this?
I would like to second this vote. Unless somebody is already working on this(?)
I will try and come up with a patch.
Regards,
Brix
--
Henrik Brix A
This LICENSE stuff is beginning to look more complex than it seemed at
first.
From this thread I gather that maintainers are going to have to do a bit
more than simply check a box. Here, for example, we see some well-known
licenses that don't readily identify themselves as such. How can a
ma
Hi--
On Jun 14, 2010, at 4:10 PM, Doug Barton wrote:
> On 06/14/10 09:59, Chuck Swiger wrote:
>> On Jun 14, 2010, at 1:07 AM, Doug Barton wrote:
>>> I'm working on adding LICENSE information to my ports, and have a
>>> few questions. A lot of my ports are ISC products, and they have
>>> the follow
On 06/14/10 09:59, Chuck Swiger wrote:
Hi--
On Jun 14, 2010, at 1:07 AM, Doug Barton wrote:
I'm working on adding LICENSE information to my ports, and have a
few questions. A lot of my ports are ISC products, and they have
the following: http://people.freebsd.org/~dougb/COPYRIGHT.txt
Yes, tha
On 06/14/10 08:05, Ashish SHUKLA wrote:
Doug Barton writes:
[...]
Then there is security/libassuan which seems to be dual licensed under
GPLv3 and LGPLv2, did we ever decide how to handle that?
In one of the dual-licensed port's Makefile, I added:
#v+
LICENSE= GPLv3 LGPL3
LICENSE_FILE_GPLv3
Hi--
On Jun 14, 2010, at 1:07 AM, Doug Barton wrote:
> I'm working on adding LICENSE information to my ports, and have a few
> questions. A lot of my ports are ISC products, and they have the following:
> http://people.freebsd.org/~dougb/COPYRIGHT.txt
Yes, that's the ISC license, http://www.ope
Doug Barton writes:
[...]
> Then there is security/libassuan which seems to be dual licensed under
> GPLv3 and LGPLv2, did we ever decide how to handle that?
In one of the dual-licensed port's Makefile, I added:
#v+
LICENSE= GPLv3 LGPL3
LICENSE_FILE_GPLv3= ${WRKSRC}/COPYING
LICENSE_FILE_LGP
20 matches
Mail list logo
