public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: justin <jlec@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] making the stable tree more up-to-date
Date: Fri, 16 Dec 2011 12:46:23 +0100	[thread overview]
Message-ID: <4EEB2F8F.2000504@gentoo.org> (raw)
In-Reply-To: <2952499.vjcSCuKqgc@devil>

[-- Attachment #1: Type: text/plain, Size: 1368 bytes --]

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


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]

  reply	other threads:[~2011-12-16 11:47 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-21  8:41 [gentoo-dev] making the stable tree more up-to-date "Paweł Hajdan, Jr."
2011-11-21 11:48 ` Ulrich Mueller
2011-11-21 12:14 ` Andreas K. Huettel
2011-11-21 12:24   ` "Paweł Hajdan, Jr."
2011-11-21 12:27   ` Rich Freeman
2011-11-21 13:12 ` James Broadhead
2011-11-21 15:47 ` Brian Dolbec
2011-11-23 14:27 ` [gentoo-dev] " Torsten Veller
2011-11-24 15:17   ` "Paweł Hajdan, Jr."
2011-11-24 16:35     ` Ian Stakenvicius
2011-11-24 17:12       ` Rich Freeman
2011-11-24 17:26         ` Pacho Ramos
2011-11-29 12:18         ` "Paweł Hajdan, Jr."
2011-11-25 16:39 ` [gentoo-dev] " Thomas Kahle
2011-11-25 19:06   ` Mr. Aaron W. Swenson
2011-11-29 12:17   ` "Paweł Hajdan, Jr."
2011-12-16 10:42 ` justin
2011-12-16 11:06   ` Agostino Sarubbo
2011-12-16 11:10     ` Anthony G. Basile
2011-12-16 11:21       ` Agostino Sarubbo
2011-12-16 11:46         ` justin [this message]
2011-12-18 10:59           ` [gentoo-dev] checking C*FLAGS used for build (was: making the stable tree more up-to-date) Michał Górny
2011-12-16 11:07   ` [gentoo-dev] making the stable tree more up-to-date Brian Harring
2011-12-16 13:27   ` "Paweł Hajdan, Jr."
2011-12-16 13:53     ` Rich Freeman
2011-12-16 14:05       ` Andreas K. Huettel
2011-12-16 18:40         ` Tim Harder
2011-12-16 14:12     ` justin
2011-12-17 15:25       ` "Paweł Hajdan, Jr."

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4EEB2F8F.2000504@gentoo.org \
    --to=jlec@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox