On Thu, 2009-07-02 at 09:51 -0700, Jim Garlick wrote: > > We've been using our own spec file with Lustre for some time so maybe > I am not aware of how it is currently done, but normally a spec file > would do a configure; make in its %build section.
Yes. Same for our spec file. > If that is the case and configure --with-ldiskfsprogs fails without > ldiskfsprogs installed, then you would need a BuildRequires: ldiskfsprogs > because people building in a mock chroot will only have the OS base packages > plus the package's BuildRequires: packages installed in the chroot. Indeed, you are correct. All of which has given me great pause to making it a strict build time requirement. Certainly not without an "i know what i am doing" kind of option to override it. All of this is just thinking aloud anyway and it's getting exactly the kind of feedback I'd want before doing anything of the sort. b.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Lustre-discuss mailing list [email protected] http://lists.lustre.org/mailman/listinfo/lustre-discuss
