Le mardi 05 avril 2005 Ã 06:53 -0700, Wichmann, Mats D a Ãcrit : > One of the irritants in building cross-platform > pkgs is that sometimes variants in rpm defaults > (across distros) breaks stuff at build time. > This kind of thing comes up on this list now and > then... unpackaged_files_terminate_build, This one is just rpm being more strict now that it was before - the fix is just to avoid unpackaged files (which will work everywhere and is the correct thing to do anyway) > whether > or not to compress manpages, etc. This one can usually be taken care of by careful %file naming > Fairly easily smoothed out with a local rpmmacros > file, If you _really_ need custom macros you can always put them in a custom macros package and buildrequire it. But this needs work - the examples you gave would certainly be easier to fix by cleaning up the specfiles instead of trying to ship ugly macro workarounds. Now a macro package to unify packaging policy is something else entirely. Regards, -- Nicolas Mailhot
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
