From: Markos Chandras <hwoarang@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: qa@gentoo.org
Subject: [gentoo-dev] Re: Add --hash-style=gnu to LDFLAGS
Date: Wed, 11 Aug 2010 00:53:52 +0300 [thread overview]
Message-ID: <20100810215352.GA7980@Mystical> (raw)
In-Reply-To: <1281201535.29176.45.camel@yamato.local>
[-- Attachment #1: Type: text/plain, Size: 1134 bytes --]
>
> It seems like few of our fellow developers don't know how to track
> down
> packages that don't respect LDFLAGS. Adding -Wl,--hash-style=gnu is a
> good way
> to do that. I would like to see this linker flag enabled by default on
> LDFLAGS
> (or at least for the dev/ profiles for now). Do you agree?
>
I would really really *really* appreciated if our beloved arch testers ( at least for linux amd64/x86
because they are the first who stabilize a package ) make this default
on their build boxes. It is annoying to mark a package stable when it has
*clear* QA problems.
Please make your build box stricter on QA rules and don't
mark a package stable that easy. Marking a package stable with multiple QA
warnings, is forcing QA team to either fix a *stable* package, which is
violating the policy, or doing some useless revbumps to fix QA issues which shouldn't be there if arch testers did
actual testing at the first place
Thanks
--
Markos Chandras (hwoarang)
Gentoo Linux Developer
Web: http://hwoarang.silverarrow.org
Key ID: 441AC410
Key FP: AAD0 8591 E3CD 445D 6411 3477 F7F7 1E8E 441A C410
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-08-10 21:53 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-07 16:32 [gentoo-dev] Add --hash-style=gnu to LDFLAGS Markos Chandras
2010-08-07 16:35 ` Tomáš Chvátal
2010-08-07 16:37 ` Alexis Ballier
2010-08-07 16:48 ` Markos Chandras
2010-08-07 18:59 ` Alexis Ballier
2010-08-07 22:08 ` Mike Frysinger
2010-08-07 17:18 ` [gentoo-dev] " Diego Elio “Flameeyes” Pettenò
2010-08-10 21:53 ` Markos Chandras [this message]
2010-08-10 22:31 ` Mike Frysinger
2010-08-11 9:11 ` Markos Chandras
2010-08-11 10:42 ` Thilo Bangert
2010-08-12 8:35 ` Christian Faulhammer
2010-08-13 15:11 ` Markos Chandras
2010-08-14 3:43 ` Ryan Hill
2010-08-14 3:50 ` Ryan Hill
2010-08-14 9:23 ` Markos Chandras
2010-08-14 4:14 ` Mike Frysinger
2010-08-14 6:41 ` Ryan Hill
2010-08-14 6:40 ` Mike Frysinger
2010-08-14 12:08 ` Markos Chandras
2010-08-14 17:58 ` Mike Frysinger
2010-08-14 18:05 ` Markos Chandras
2010-08-14 18:31 ` Samuli Suominen
2010-08-14 18:34 ` Mike Frysinger
2010-08-14 19:46 ` Markos Chandras
2010-08-15 7:31 ` Christian Faulhammer
2010-08-07 21:32 ` Mike Frysinger
2010-08-08 0:11 ` Markos Chandras
2010-08-08 0:15 ` Alec Warner
2010-08-08 0:21 ` Markos Chandras
2010-08-08 7:57 ` Petteri Räty
2010-08-08 8:37 ` Ryan Hill
2010-08-08 0:22 ` Diego Elio Pettenò
2010-08-08 0:19 ` Diego Elio Pettenò
2010-08-08 11:12 ` Markos Chandras
2010-08-08 2:16 ` Mike Frysinger
2010-08-08 11:14 ` Markos Chandras
2010-08-09 23:03 ` Markos Chandras
2010-08-09 23:05 ` Mike Frysinger
2010-08-10 8:45 ` Brian Harring
2010-08-10 18:40 ` Francesco R
2010-08-10 20:09 ` Mike Frysinger
2010-08-10 20:16 ` Mike Frysinger
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=20100810215352.GA7980@Mystical \
--to=hwoarang@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=qa@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