On Saturday 02 June 2007, Jesse Keating wrote: > On Friday 01 June 2007 19:42:21 Dennis Gilmore wrote: > > buildsys-macros still exists with only > > printf %s%b "%" "__arch_install_post /usr/lib/rpm/check-buildroot\n" >> > > $RPM_BUILD_ROOT/etc/rpm/macros.checkbuild > > > > so we can still run check-buildroot at least for mock builds.. > > Right, and we can split the check-buildroot out into it's own package or > whatnot so that we can do that on user's systems too, but not pull in all > of what currently provides check-buildroot. We talked about that before on > one of the lists. Splitting is trivial, I have plans to work on this soon in rpmdevtools, but automatically enabling eg. check-buildroot if the package is installed is trickier. I don't think we can define __arch_install_post automatically (ie. "claim ownership of the macro") for all systems. If the system already had __arch_install_post set to something in let's say /etc/rpm/macros, what happens? What about ~/.rpmmacros? -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
