Re: using security/openssl in a port

2018-01-05 Thread Eugene Grosbein
05.01.2018 11:16, Matthew Luckie пишет: > On 1/5/18 5:09 PM, Eugene Grosbein wrote: >> On 05.01.2018 09:44, Matthew Luckie wrote: >> >>> My main worry is that I could not find a single port that apparently >>> depends on security/openssl. I'm worried that its more complicated than >>> simply decla

Re: using security/openssl in a port

2018-01-05 Thread Mathieu Arnold
Le 05/01/2018 à 03:11, Matthew Luckie a écrit : > Hi, > > I maintain a port that has a new release which requires openssl 1.0.2 to > build. FreeBSD 10.3 and 10.4 both have openssl 1.0.1, and 11 onwards > have 1.0.2. Is there a magic way to have this port depend on ports > openssl for freebsd rele

Re: using security/openssl in a port

2018-01-04 Thread Chris H
On Fri, 5 Jan 2018 17:16:30 +1300 "Matthew Luckie" said On 1/5/18 5:09 PM, Eugene Grosbein wrote: > On 05.01.2018 09:44, Matthew Luckie wrote: > >> My main worry is that I could not find a single port that apparently >> depends on security/openssl. I'm worried that its more complicated than

Re: using security/openssl in a port

2018-01-04 Thread Matthew Luckie
On 1/5/18 5:09 PM, Eugene Grosbein wrote: > On 05.01.2018 09:44, Matthew Luckie wrote: > >> My main worry is that I could not find a single port that apparently >> depends on security/openssl. I'm worried that its more complicated than >> simply declaring a dependency on security/openssl on parti

Re: using security/openssl in a port

2018-01-04 Thread Eugene Grosbein
On 05.01.2018 09:44, Matthew Luckie wrote: > My main worry is that I could not find a single port that apparently > depends on security/openssl. I'm worried that its more complicated than > simply declaring a dependency on security/openssl on particular freebsd > versions because other ports that

Re: using security/openssl in a port

2018-01-04 Thread Matthew Luckie
On 01/05/18 15:37, Chris H wrote: > On Fri, 5 Jan 2018 15:11:00 +1300 "Matthew Luckie" said > >> Hi, >> >> I maintain a port that has a new release which requires openssl 1.0.2 to >> build.  FreeBSD 10.3 and 10.4 both have openssl 1.0.1, and 11 onwards >> have 1.0.2.  Is there a magic way to have

Re: using security/openssl in a port

2018-01-04 Thread Chris H
On Fri, 5 Jan 2018 15:44:31 +1300 "Matthew Luckie" said On 01/05/18 15:37, Chris H wrote: > On Fri, 5 Jan 2018 15:11:00 +1300 "Matthew Luckie" said > >> Hi, >> >> I maintain a port that has a new release which requires openssl 1.0.2 to >> build.  FreeBSD 10.3 and 10.4 both have openssl 1.0.1

Re: using security/openssl in a port

2018-01-04 Thread Chris H
On Fri, 5 Jan 2018 15:11:00 +1300 "Matthew Luckie" said Hi, I maintain a port that has a new release which requires openssl 1.0.2 to build. FreeBSD 10.3 and 10.4 both have openssl 1.0.1, and 11 onwards have 1.0.2. Is there a magic way to have this port depend on ports openssl for freebsd rel

Re: using security/openssl in a port

2018-01-04 Thread Eugene Grosbein
05.01.2018 9:11, Matthew Luckie wrote: > I maintain a port that has a new release which requires openssl 1.0.2 to > build. FreeBSD 10.3 and 10.4 both have openssl 1.0.1, and 11 onwards > have 1.0.2. Is there a magic way to have this port depend on ports > openssl for freebsd releases without ope

using security/openssl in a port

2018-01-04 Thread Matthew Luckie
Hi, I maintain a port that has a new release which requires openssl 1.0.2 to build. FreeBSD 10.3 and 10.4 both have openssl 1.0.1, and 11 onwards have 1.0.2. Is there a magic way to have this port depend on ports openssl for freebsd releases without openssl 1.0.2? I ran find /usr/ports -exec g