From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] move openssl.cnf file into base openssl package
Date: Thu, 16 Dec 2010 15:10:37 +0100 [thread overview]
Message-ID: <ied6kt$dqa$1@dough.gmane.org> (raw)
In-Reply-To: <131E5DFBE7373E4C8D813795A6AA7F080329E92ADA@dlee06.ent.ti.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 16-12-10 15:04, Maupin, Chase wrote:
>> -----Original Message-----
>> From: openembedded-devel-bounces@lists.openembedded.org
>> [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of
>> Roman I Khimov
>> Sent: Wednesday, December 15, 2010 2:39 PM
>> To: openembedded-devel@lists.openembedded.org
>> Subject: Re: [oe] [RFC] move openssl.cnf file into base openssl package
>>
>> В сообщении от Среда 15 декабря 2010 22:47:05 автор Maupin, Chase написал:
>>>> 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.
>>
>> openssl is rdepending on libcrypto anyway (it's linked with it and I don't
>> think it'll change any time soon). But configs for different versions can
>> be
>> conflicting, so I'm not sure this kind of approach solves anything.
>
> I noticed that. I think the only thing that putting this into its own package would solve is addressing Koen's comment about having multiple versions of libcrypto installed.
>
> Koen, can you comment on your change that moved the openssl.cnf file to the misc package? Do you still need to be able to install multiple versions of libcrypto?
Yes, I still need to be able to do that, couldn't you just add an
rrecommend for -misc?
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFNCh3dMkyGM64RGpERAseRAJ9KEl9B6YuGjRmZNzK3mFGhMZlAlwCfYJqK
1MNv3HdFqJteWCrn+kFD48Q=
=eo6B
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-12-16 14:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 18:38 [RFC] move openssl.cnf file into base openssl package Maupin, Chase
2010-12-15 19:40 ` Roman I Khimov
2010-12-15 19:47 ` Maupin, Chase
2010-12-15 20:39 ` Roman I Khimov
2010-12-16 14:04 ` Maupin, Chase
2010-12-16 14:10 ` Koen Kooi [this message]
2010-12-16 14:32 ` Roman I Khimov
2010-12-16 14:30 ` Maupin, Chase
2010-12-16 14:56 ` Roman I Khimov
2010-12-16 15:16 ` Maupin, Chase
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ied6kt$dqa$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.