2008/2/10 Axel Thimm <Axel.Thimm@xxxxxxxxxx>: > On Sun, Feb 10, 2008 at 11:44:18AM -0600, Paul Johnson wrote: > > On 2/10/08, Tony Earnshaw <tonni@xxxxxxxxx> wrote: > > > rpm@xxxxxxxxxxxxxxxxxxxxxxxxx skrev, on 10-02-2008 12:46: > > > > > > > I'm trying to rebuild some src rpms that I d/l'ed from atrpms. > > > > > > > > Their spec files have a "%kmdl" directive in them. > > > > > > > > how might I handle this ? > > Install atrpms-rpm-config. As well as any kernel headers/sources you > need to build kmdls for. > > > I've run into this many times. My solution is avoid ATRPMs at all > > cost. AT created his own rpm macro scheme and unless you install his > > devel packages, you will have trouble. So I avoid them. > > What's wrong with defining macros? Nowadays even cmake defines its own > macros (nothing against cmake or its macros), and a more complex setup > like kernel modules is in need for abstaction even more so. > -- What's wrong? One needs to install your package of macros on every machine on which rpms are to be created. In a fast moving environment where one is managing a lot of different kinds of rpm systems (some Fedora, Scientifc Linux, some RedHat of various generations), it is easiest to rely on the default macros that work all of the time to build RPMs. On some systems, I don't have root permissions, and can build RPMs in my account. The ATrpms config package can't be installed there, and I'm totally dead in the water. Sometimes people allow me to log into their systems as a user and build a package for other people who have that same system, but I can't install special macros on those systems just to build an RPM. And I do perfectly fine RPMS with the standard macros. I have trouble not only with ATrpms, but also Mandriva and SUSE for this reason. pj -- Paul E. Johnson Professor, Political Science 1541 Lilac Lane, Room 504 University of Kansas _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
