1 |
Nikos Chantziaras <realnc@×××××.de> wrote: |
2 |
> |
3 |
> If you use portage than you can control per-package CFLAGS using |
4 |
> bashrc and /etc/portage/env or similar functionality. |
5 |
|
6 |
This is correct, but the problem is that an ebuild author or |
7 |
upstream cannot set a "default" here: IMHO, it shouldn't be |
8 |
necessary for the user to use such things only in order to |
9 |
compile a package with the CFLAGS which upstream recommends. |
10 |
Normally, users will not read such a recommendation (and in fact, |
11 |
they shouldn't have to, since reading INSTALL or similar things |
12 |
should be the task of the ebuild author). |
13 |
|
14 |
Speaking from the author's perspective: There should be a way |
15 |
to write code appropriate for a specific compiler flag and to |
16 |
assume that most users will then actually compile the package |
17 |
with the corresponding flag. |
18 |
If a user explicitly does not want to do this, this is fine, |
19 |
but the ebuild should have a way to make sure that this only |
20 |
happens if it is really the intention of the user. |
21 |
Normally, USE flags are the way to pass options to the |
22 |
user, aren't they? |
23 |
|
24 |
Best Regards |
25 |
Martin Väth |