[oe] [RFC] move openssl.cnf file into base openssl package

[Maupin, Chase]

> -----Original Message-----
> From: openembedded-devel-bounces at lists.openembedded.org
> [mailto:openembedded-devel-bounces at lists.openembedded.org] On Behalf Of
> Roman I Khimov
> Sent: Wednesday, December 15, 2010 1:41 PM
> To: openembedded-devel at lists.openembedded.org
> Subject: Re: [oe] [RFC] move openssl.cnf file into base openssl package
> 
> В сообщении от Среда 15 декабря 2010 21:38:07 автор Maupin, Chase написал:
> > From the log I see that the openssl.cnf file was originally added to the
> >  libcrypto package since it was accessed directly from libcrypto (commit
> >  f95a95435ca79e7b9942b6e321d30e264c728791).  I then see that it was
> moved
> >  the file to the misc package to make different libcrypto versions
> parallel
> >  installable (commit 26b7d6514111d5ac0171c1834fa85d4576d783bf) but no
> other
> >  justification as to why the .cnf was placed in the misc instead of base
> >  package.
> >
> > I have a patch to move the openssl.cnf file into the openssl package but
> I
> >  wanted to better understand why this file was not already in the
> openssl
> >  package before submitting my patch.
> 
> Missed that change. Seems wrong to me. And I still think that it belongs
> to
> libcrypto, not openssl since you can easily not install openssl binary and
> still use it with tuned openssl.cnf in your apps.

So it seems like there are two packages that need this default openssl.cnf file, the libcrypto and openssl packages.  Would it perhaps be a better idea to pull the configuration file into its own package and then set the RDEPENDS for the libcrypto and openssl packages to use the openssl configuration package?  That way you can still have multiple versions of libcrypto (like Koen was trying to do) and have the default file shared between both packages that need it.

> 
> --
>  http://roman.khimov.ru
> mailto: roman at khimov.ru
> gpg --keyserver hkp://subkeys.pgp.net --recv-keys 0xE5E055C3