On Wed, Mar 27, 2019 at 05:03:23PM +0100, Georg Sauthoff wrote:
> On Wed, Mar 27, 2019 at 03:04:53PM +, Richard W.M. Jones wrote:
> > On Tue, Mar 26, 2019 at 06:07:05PM +0100, Georg Sauthoff wrote:
> > > because rpm automatically adds something like:
> > >
> > > libfoo.so.1()(64bit)
> > >
On Wed, Mar 27, 2019 at 03:04:53PM +, Richard W.M. Jones wrote:
> On Tue, Mar 26, 2019 at 06:07:05PM +0100, Georg Sauthoff wrote:
> > because rpm automatically adds something like:
> >
> > libfoo.so.1()(64bit)
> >
> > Of course, I could still add a superfluous
> >
> > Requires:
On Tue, Mar 26, 2019 at 06:07:05PM +0100, Georg Sauthoff wrote:
> because rpm automatically adds something like:
>
> libfoo.so.1()(64bit)
>
> Of course, I could still add a superfluous
>
> Requires: libfoo
This could pull in the 32 bit version of the package so it's wrong as
well as
Georg Sauthoff wrote:
> Hello,
>
> when packaging a C/C++ program, the rpm automatic dependency feature
> usually works well for shared libraries.
>
> That mean when program 'bar' needs libfoo-devel at build time it's
> sufficient to add
>
> BuildRequires: libfoo-devel
>
> and I can omit
Hello,
when packaging a C/C++ program, the rpm automatic dependency feature
usually works well for shared libraries.
That mean when program 'bar' needs libfoo-devel at build time it's
sufficient to add
BuildRequires: libfoo-devel
and I can omit
Requires: libfoo
because rpm
