1 |
On 23 June 2014 01:02, Duncan <1i5t5.duncan@×××.net> wrote: |
2 |
|
3 |
> |
4 |
> The usual conditional for that is USE=custom-cflags or a similar variant |
5 |
> like custom-optimization. See the firefox ebuilds, which use both. |
6 |
> |
7 |
> $ equery -N u firefox | grep custom |
8 |
> - - custom-cflags : Build with user-specified CFLAGS (unsupported) |
9 |
> + + custom-optimization : Fine-tune custom compiler optimizations (-Os, |
10 |
> -O0, -O1, -O2, -O3) |
11 |
> |
12 |
> |
13 |
> Generally, such USE flags are discouraged in gentoo, where honoring a |
14 |
> user's CFLAGS, etc. and letting them keep the pieces if it comes to that |
15 |
> is the norm. Where upstream refuses to support custom cflags, however, |
16 |
> the USE flag solution seems to be an accepted at maintainer discretion. |
17 |
|
18 |
|
19 |
|
20 |
The problem with a USE flag here as such is the change this eclass makes |
21 |
affects >900 packages in dev-perl/ , and its not easy to casually determine |
22 |
which of those packages have any C bits where CFLAGS are even meaningful. |
23 |
|
24 |
Which would mean having >900 packages with a new IUSE value that did |
25 |
nothing for a majority of them. |
26 |
|
27 |
|
28 |
-- |
29 |
Kent |