[openib-general] Suggested components to support in 1.0

Doug Ledford dledford at redhat.com
Mon Feb 27 15:28:31 PST 2006


On Fri, Feb 24, 2006 at 01:45:57PM -0800, Matt L. Leininger wrote:
> On Fri, 2006-02-24 at 09:57 -0800, Bryan O'Sullivan wrote:
> > On Fri, 2006-02-24 at 09:52 -0800, Bob Woodruff wrote:
> > > Bryan wrote,
> > > >Do you want the diags in, or out?  They're not packaged in any way, so
> > > >I'd vote for "out".
> > > 
> > > Again, I would vote for including everything that is in the trunk
> > > unless the maintainer decides it is not ready or it is some 
> > > code that is now obsolete and should be removed.
> > 
> > I don't have a problem with leaving code in the SVN branch and not
> > touching it.  My point is more that the management diags don't have an
> > RPM spec file, so if someone doesn't write one, they won't get shipped
> > in binary form, and hence they won't get tested or used.  This applies
> > to other components, too.
> 
>   Agreed.  Is anyone planning on adding a spec file for the tools and
> diags?

My spec files for both libibverbs and opensm include the related utilities
and diags.  My one suggestion is that if you bother to create spec files for
a 1.0 release, then please don't use /usr/local, use the proper locations
for files as though they were something other than 1 off local builds.  For
example all the scripts in the management tree use /usr/local as their
prefix, the configure program doesn't change them, so my rpm has a shell
environment file it drops in /etc/profile.d in order to get the scripts to
work without having to edit all the paths.  I'd prefer not to have to have
that file in /etc/profile.d for an official 1.0 release ;-)

-- 
  Doug Ledford <dledford at redhat.com>     919-754-3700 x44233
         Red Hat, Inc. 
         1801 Varsity Dr.
         Raleigh, NC 27606
  



More information about the general mailing list