1 |
On 02/01/2017 01:03 PM, Michał Górny wrote: |
2 |
> W dniu 01.02.2017, śro o godzinie 09∶06 -0800, użytkownik Zac Medico |
3 |
> napisał: |
4 |
>> The native-extensions USE flag will enable building of the |
5 |
>> libc bindings. This is not enabled by default because it does |
6 |
>> not support cross compilation. |
7 |
>> |
8 |
>> X-Gentoo-bug: 571444 |
9 |
>> X-Gentoo-bug-url: https://bugs.gentoo.org/show_bug.cgi?id=571444 |
10 |
>> --- |
11 |
>> sys-apps/portage/metadata.xml | 1 + |
12 |
>> sys-apps/portage/portage-9999.ebuild | 7 ++++++- |
13 |
>> 2 files changed, 7 insertions(+), 1 deletion(-) |
14 |
>> |
15 |
>> diff --git a/sys-apps/portage/metadata.xml b/sys- |
16 |
>> apps/portage/metadata.xml |
17 |
>> index e032ea5..882d3ba 100644 |
18 |
>> --- a/sys-apps/portage/metadata.xml |
19 |
>> +++ b/sys-apps/portage/metadata.xml |
20 |
>> @@ -12,6 +12,7 @@ |
21 |
>> <use> |
22 |
>> <flag name="epydoc">Build html API documentation with |
23 |
>> epydoc.</flag> |
24 |
>> <flag name="ipc">Use inter-process communication between portage |
25 |
>> and running ebuilds.</flag> |
26 |
>> + <flag name="native-extensions">Build native extensions. Cross- |
27 |
>> compilation is not supported.</flag> |
28 |
>> <flag name="xattr">Preserve extended attributes (filesystem- |
29 |
>> stored metadata) when installing files. Usually only required for |
30 |
>> hardened systems.</flag> |
31 |
>> </use> |
32 |
>> </pkgmetadata> |
33 |
>> diff --git a/sys-apps/portage/portage-9999.ebuild b/sys- |
34 |
>> apps/portage/portage-9999.ebuild |
35 |
>> index 6a6f515..981db26 100644 |
36 |
>> --- a/sys-apps/portage/portage-9999.ebuild |
37 |
>> +++ b/sys-apps/portage/portage-9999.ebuild |
38 |
>> @@ -19,7 +19,7 @@ HOMEPAGE="https://wiki.gentoo.org/wiki/Project:Porta |
39 |
>> ge" |
40 |
>> LICENSE="GPL-2" |
41 |
>> KEYWORDS="" |
42 |
>> SLOT="0" |
43 |
>> -IUSE="build doc epydoc +ipc linguas_ru selinux xattr" |
44 |
>> +IUSE="build doc epydoc +ipc linguas_ru native-extensions selinux |
45 |
>> xattr" |
46 |
> |
47 |
> Wouldn't it be better to enable it by default? |
48 |
|
49 |
Yeah, that should be fine. We may get a few duplicates of bug 594744 |
50 |
reported, but that's no reason not to enable it by default. |
51 |
-- |
52 |
Thanks, |
53 |
Zac |