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