On 12/16/11 12:21 PM, Agostino Sarubbo wrote: > On Friday 16 December 2011 06:10:13 Anthony G. Basile wrote: >> Does your script do any checking on the quality of the ebuild, eg that >> it respects C/LDFLAGS. If so, that's useful and would help package >> maintainers to better prepare their ebuilds for stabilization. > Unfortunately no. > > For LDFLAGS there is a QA warning and is enough visible > For CFLAGS I see with the naked eye a bit of build log > My script at "end of work" just runs repoman full and cat entire ebuild( so, > imho, should be a tasks already done by maintainers). > Finally, I take a look at the ebuild to see if there are issue(s) > > This is all. > >> And congrats on making dev > Thanks ;) > > > Regards > Agostino
You can use the post* hooks for that. For FLAGS mixing I am using CFLAGS and CXXFLAGS specific warning flags during compilation and grep for the gcc mixing warning in the build log. Probably similar things can be done for other problematic points. There was also a more sophisticated approach Diego blogged about. For respecting C/CXXFLAGS there was something Donnie suggested long ago. If you use -frecord-gcc-switches you are able to read the used LFGAS with eu-readelf. Probably someone likes to put this together in a guideline how to check a package correctly. justin
signature.asc
Description: OpenPGP digital signature
