Re: [gentoo-portage-dev] [PATCH] Ignore setup.cfg and *.so

2017-02-14 Thread Brian Dolbec 
On Tue, 14 Feb 2017 12:02:18 -0500
Mike Gilbert  wrote:

> This allows one to compile the extension modules in-place without
> having the build artifacts show up in git status.
> 
> For example:
> printf "[build_ext]\nportage-ext-modules = true\n" > setup.cfg
> python setup.py build_ext --inplace
> ---
>  .gitignore | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/.gitignore b/.gitignore
> index 930252f66..9c13ef473 100644
> --- a/.gitignore
> +++ b/.gitignore
> @@ -1,7 +1,9 @@
>  *.py[co]
>  __pycache__/
>  *.class
> +*.so
>  /build
>  /tags
> +setup.cfg
>  
>  repoman/build


looks good, push please :)
-- 
Brian Dolbec

Re: [gentoo-portage-dev] [PATCH] sys-apps/portage: add native-extensions USE flag (bug 571444)

2017-02-14 Thread Mike Gilbert 
On Wed, Feb 1, 2017 at 4:15 PM, Zac Medico  wrote:
> On 02/01/2017 01:03 PM, Michał Górny wrote:
>> W dniu 01.02.2017, śro o godzinie 09∶06 -0800, użytkownik Zac Medico
>> napisał:
>>> The native-extensions USE flag will enable building of the
>>> libc bindings. This is not enabled by default because it does
>>> not support cross compilation.
>>>
>>> X-Gentoo-bug: 571444
>>> X-Gentoo-bug-url: https://bugs.gentoo.org/show_bug.cgi?id=571444
>>> ---
>>>  sys-apps/portage/metadata.xml| 1 +
>>>  sys-apps/portage/portage-.ebuild | 7 ++-
>>>  2 files changed, 7 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/sys-apps/portage/metadata.xml b/sys-
>>> apps/portage/metadata.xml
>>> index e032ea5..882d3ba 100644
>>> --- a/sys-apps/portage/metadata.xml
>>> +++ b/sys-apps/portage/metadata.xml
>>> @@ -12,6 +12,7 @@
>>>
>>>  Build html API documentation with
>>> epydoc.
>>>  Use inter-process communication between portage
>>> and running ebuilds.
>>> +Build native extensions. Cross-
>>> compilation is not supported.
>>>  Preserve extended attributes (filesystem-
>>> stored metadata) when installing files. Usually only required for
>>> hardened systems.
>>>
>>>  
>>> diff --git a/sys-apps/portage/portage-.ebuild b/sys-
>>> apps/portage/portage-.ebuild
>>> index 6a6f515..981db26 100644
>>> --- a/sys-apps/portage/portage-.ebuild
>>> +++ b/sys-apps/portage/portage-.ebuild
>>> @@ -19,7 +19,7 @@ HOMEPAGE="https://wiki.gentoo.org/wiki/Project:Porta
>>> ge"
>>>  LICENSE="GPL-2"
>>>  KEYWORDS=""
>>>  SLOT="0"
>>> -IUSE="build doc epydoc +ipc linguas_ru selinux xattr"
>>> +IUSE="build doc epydoc +ipc linguas_ru native-extensions selinux
>>> xattr"
>>
>> Wouldn't it be better to enable it by default?
>
> Yeah, that should be fine. We may get a few duplicates of bug 594744
> reported, but that's no reason not to enable it by default.

+1 on enabling native-extensions by default. The cross-compiling
community is a small minority, and we should not base the default on
their use case.

[gentoo-portage-dev] [PATCH] Ignore setup.cfg and *.so

2017-02-14 Thread Mike Gilbert 
This allows one to compile the extension modules in-place without having
the build artifacts show up in git status.

For example:
printf "[build_ext]\nportage-ext-modules = true\n" > setup.cfg
python setup.py build_ext --inplace
---
 .gitignore | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/.gitignore b/.gitignore
index 930252f66..9c13ef473 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,7 +1,9 @@
 *.py[co]
 __pycache__/
 *.class
+*.so
 /build
 /tags
+setup.cfg
 
 repoman/build
-- 
2.11.1