[Pkg-openssl-devel] OpenSSL RT#4130: 'enginesdir' pkgconfig variable

Kurt Roeckx kurt at roeckx.be
Sat Sep 24 18:30:25 UTC 2016


On Sat, Sep 24, 2016 at 07:13:26PM +0100, David Woodhouse wrote:
> On Sun, 2016-09-18 at 23:49 +0200, Kurt Roeckx wrote:
> > On Sun, Sep 18, 2016 at 08:06:29PM +0100, David Woodhouse wrote:
> > > 
> > > On Sun, 2016-09-18 at 20:51 +0200, Kurt Roeckx wrote:
> > > > 
> > > > On Tue, Sep 13, 2016 at 10:12:52AM +0100, David Woodhouse wrote:
> > > > > 
> > > > >  
> > > > > In fact you can even start adding enginesdir to libcrypto.pc straight
> > > > > away, without updating to a new release.
> > > > >  
> > > > > This was https://github.com/openssl/openssl/pull/1501
> > > > As far as I know this got merged upstream.  Is there a reason you
> > > > can't just wait for the next upstream release?
> > > None whatsoever. The main point of my mail was to make sure you were
> > > aware of its presence in the next upstream release  — since I believe
> > > you have local patching to make it use a *different* enginesdir, and
> > > wanted to make sure you notice that you now need to patch libcrypto.pc
> > > (or whatever creates it) too.
> > I guess it depends on how it's it ends up in libcrypto.pc.  In any
> > case, for 1.1.0 it's not modified.  If 1.0.2 also adds it, I will
> > need to look at it, and I guess I might forget about it.
> 
> Well, that happened quicker than I anticipated. OpenSSL 1.0.2i came out
> on Thursday, and has enginesdir in libcrypto.pc.
> 
> Don't forget about it :)

It's already uploaded to unstable and jessie-backports, it should
have it correctly in it I think.


Kurt




More information about the Pkg-openssl-devel mailing list