В сообщении от Среда 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.

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

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Reply via email to