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

Maupin, Chase chase.maupin at ti.com
Thu Dec 16 15:16:11 UTC 2010


> -----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: Thursday, December 16, 2010 8:57 AM
> To: openembedded-devel at lists.openembedded.org
> Subject: Re: [oe] [RFC] move openssl.cnf file into base openssl package
> 
> В сообщении от Четверг 16 декабря 2010 17:30:58 автор 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: Thursday, December 16, 2010 8:32 AM
> > > To: openembedded-devel at lists.openembedded.org
> > > Subject: Re: [oe] [RFC] move openssl.cnf file into base openssl
> package
> > >
> > > В сообщении от Четверг 16 декабря 2010 17:10:37 автор Koen Kooi
> написал:
> > > > >>> 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?
> > >
> > > To get all -misc stuff? I'd opt for putting openssl.cnf in its own
> > > package and
> > > setting it as RRECOMMENDS for libcrypto in that case.
> >
> > Agreed.  Although would you say RRECOMMENDS or RDEPENDS?
> 
> I've just said above, RRECOMMENDS. Most applications using libcrypto can
> work
> without a default config file. They even worked for a long time before
> I've
> packaged it. But you get it installed by default with RRECOMMENDS, and
> only if
> you know what you're doing you add it in BAD_RECOMMENDATIONS or delete it
> in
> some other way.
> 
> Speaking of which, it should also be listed in CONFFILES, missed that in
> March.

I'll submit a patch for this today.  Thanks for the input.

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


More information about the Openembedded-devel mailing list