Date: Thu, 04 Jan 2018 18:56:07 -0800 From: "Chris H" <portmaster@BSDforge.com> To: "Matthew Luckie" <mjl@luckie.org.nz> Cc: <freebsd-ports@freebsd.org> Subject: Re: using security/openssl in a port Message-ID: <e8c5a68c746be6f9fa84b2e661648b97@udns.ultimatedns.net> In-Reply-To: <3677cb37-8cc2-60c0-3e23-55fa507a4465@luckie.org.nz>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 5 Jan 2018 15:44:31 +1300 "Matthew Luckie" <mjl@luckie=2Eorg=2Enz> said
> On 01/05/18 15:37, Chris H wrote:
> > On Fri, 5 Jan 2018 15:11:00 +1300 "Matthew Luckie" <mjl@luckie=2Eorg=2Enz> =
said
> >=20
> >> Hi,
> >>
> >> I maintain a port that has a new release which requires openssl 1=2E0=2E2 =
to
> >> build=2E=C2=A0 FreeBSD 10=2E3 and 10=2E4 both have openssl 1=2E0=2E1, and 11 onw=
ards
> >> have 1=2E0=2E2=2E=C2=A0 Is there a magic way to have this port depend on por=
ts
> >> openssl for freebsd releases without openssl 1=2E0=2E2?=C2=A0 I ran
> >>
> >> find /usr/ports -exec grep "security/openssl" {} \; -print
> >>
> >> and didn't find anything that I could use as a recipe=2E=C2=A0 USES =3D =
ssl
> >> doesn't seem to be it either=2E
> >>
> >> Matthew
> > Hello Matthew,
> > Have a look at ports/Mk/bsd=2Eport=2Emk
> > In there you will find some clues for defining rules for building
> > for specific (bsd)OS versions -- like >=3DXXXXX, or =2Eif OSREL <=3DXXXXX=
X =2E=2E=2E
> > As well as only permitting build/install when the correct version
> > of security/openssl is found in the systems ports tree=2E
> > It's well commented, and should give you some good options to try=2E
> > It will also give some good clues to search the ports tree for=2E Where
> > you can simply copy someone else's work verbatim=2E :-)
> >=20
> > You might also try the following alternative for searching;
> > cd /usr/ports
> > find =2E | xargs <string-to-search-for>
> >=20
> > HTH
>=20
> My main worry is that I could not find a single port that apparently
> depends on security/openssl=2E I'm worried that its more complicated than
> simply declaring a dependency on security/openssl on particular freebsd
> versions because other ports that use openssl might link against it
> without registering a dependency=2E Is my worry misplaced?
Openssl is a PITA=2E You *also* have to consider whether the user is using
openssl in $BASE, rather than the ports version=2E There are many variables
to consider, and I don't envy you on this=2E :-)
If you get something you think might work, feel free to ask about it=2E :-)
--Chris
>=20
> Matthew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e8c5a68c746be6f9fa84b2e661648b97>