On Thu, Oct 25, 2018 at 05:31:46PM +0200, Nicolas Morey-Chaisemartin wrote: > > > On 10/25/18 4:18 PM, Jason Gunthorpe wrote: > > On Thu, Oct 25, 2018 at 10:00:06AM -0400, Doug Ledford wrote: > >> On Wed, 2018-10-24 at 12:43 +0200, Nicolas Morey-Chaisemartin wrote: > >>> On 10/23/18 10:57 PM, Jason Gunthorpe wrote: > >>>> From: Jason Gunthorpe <jgg@xxxxxxxxxxxx> > >>>> > >>>> Now that we can produce them properly, add them. > >>>> > >>>> Signed-off-by: Jason Gunthorpe <jgg@xxxxxxxxxxxx> > >>>> > >>> SUSE packaging policy does not allow for static libraries (apart > >>> from a few rare exceptions). Thus, they shouldn't enable them > >>> by default. I'm not against adding a RPM option to enable it if > >>> needed. > >> Red Hat/Fedora have the same policy BTW. As far as Red Hat is > >> concerned, it's all about making sure that security updates to > >> libraries actually make it into use and insecure, broken > >> libraries don't stay hanging around because they are statically > >> linked into something. > > Some of the distros have asked for this, do you want to just drop the > > patches enabling this in packaging and leave it up to the packagers > > for now? > > If people have asked for this on RPM based distro, let's add a flag > (disabled by default) for both RHEL and SUSE so any outside packager > ( OFED ? ) can enable it very easily. Sure, I've never used rpmbuild flags, can you give an quick example? Jason
