On 06/05/2009 10:31 AM, Adam Williamson wrote: > It seems to me it'd make sense to convert all these kinds of snippets > into macros. Am I right, or is there a reason against doing this? > > If I'm right, I'm happy to work on this and contribute it as patches to > the relevant packages, or as a new package in itself, or something. > Where should such macros go? Should we have a separate package for them > which is brought in when you install the development environment package > set? Or should they be added to the appropriate -devel packages - e.g., > Tcl snippets should be turned into a /etc/rpm/macros.tcl that's in the > tcl-devel package? Or a combination of the two? > To some extent, yes. macros can go overboard, though. I think that the macros you're planning are going to make sense, though :-) The way to get these changed is to first go through the Packaging Committee to get the changes approved, then have the macros merged into the packages that will provide them. Then patch the packages that should be updated. Note: I remember one argument against macros being that they make spec files harder to port between distros but I'm not willing to champion that argument. If someone else does, I'll certainly listen to the reasoning, though. :-) -Toshio
Attachment:
signature.asc
Description: OpenPGP digital signature
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
