Re: Adding mk/ssl.buildlink3.mk

[David Brownlee <abs%absd.org@localhost>]

On Mon, 4 Oct 2021 at 13:16, Joerg Sonnenberger <joerg%bec.de@localhost> wrote:
>
> On Fri, Oct 01, 2021 at 09:46:14AM +0100, David Brownlee wrote:
> > Would anyone object to me making a pass through the tree to replace
> >
> > .include "../../security/openssl/buildlink3.mk"
> >
> > with
> >
> > .include "../../mk/ssl.buildlink3.mk"
> >
> > and adding a simple mk/ssl.buildlink3.mk which just includes
> > security/openssl/buildlink3.mk
>
> I don't really see the point. We can pick a second version just as
> easily from the existing security/openssl/b3.mk without all the churn.

Well
a) It's intended to grow into handling other ssl providers rather than
just openssl
b) We have a general pattern of putting this sort of buildlink3 logic
in /pkgsrc/mk - though that's not always the case. OK, cue another
mini bikeshed on what the naming pattern should be going forward
(pause this - new thread coming up)

David