-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/25/2012 10:13 PM, Michał Górny wrote:
> On Thu, 25 Oct 2012 20:55:37 +0200 hasufell
> wrote:
>
>> Currently you seem to have focused more on distutils when
>> writing python-r1 which makes this eclass a bit raw. Waiting for
>> other developers
On Thu, 25 Oct 2012 21:19:37 +0200
hasufell wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 10/25/2012 06:41 PM, hasufell wrote:
> > 1. there is still no way to convert shebangs via python-r1 2. there
> > are no equivalent functions to the python_get_* stuff which are
> > sometim
On Thu, 25 Oct 2012 20:55:37 +0200
hasufell wrote:
> On 10/25/2012 07:43 PM, Michał Górny wrote:
> > On Thu, 25 Oct 2012 18:41:47 +0200 hasufell
> > wrote:
> >
> >> 1. there is still no way to convert shebangs via python-r1
> >
> > What conversion do you expect? The docs say it clearly that th
On Thu, 25 Oct 2012 20:55:37 +0200
hasufell wrote:
> Currently you seem to have focused more on distutils when writing
> python-r1 which makes this eclass a bit raw.
> Waiting for other developers to file feature requests instead of
> figuring out those yourself before they even consider porting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/25/2012 06:41 PM, hasufell wrote:
> 1. there is still no way to convert shebangs via python-r1 2. there
> are no equivalent functions to the python_get_* stuff which are
> sometimes necessary for broken build systems or test phases 3.
> there is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/25/2012 07:43 PM, Michał Górny wrote:
> On Thu, 25 Oct 2012 18:41:47 +0200 hasufell
> wrote:
>
>> 1. there is still no way to convert shebangs via python-r1
>
> What conversion do you expect? The docs say it clearly that the
> eclass will be e
On Thu, 25 Oct 2012 18:41:47 +0200
hasufell wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> 1. there is still no way to convert shebangs via python-r1
What conversion do you expect? The docs say it clearly that the eclass
will be extended on request, so please file a clear request
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 25/10/12 12:41 PM, hasufell wrote:
> 6. How can I make the python dependencies optional, e.g. that
> python:3.2 is only pulled in when gtk useflag for this package is
> set?
that's not so much an optional dependency as an enforcement of a
PYHTON
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
1. there is still no way to convert shebangs via python-r1
2. there are no equivalent functions to the python_get_* stuff which
are sometimes necessary for broken build systems or test phases
3. there is no equivalent for python_mod_optimize. Having th
On Sat, 29 Sep 2012 10:53:29 +0200
Michał Górny wrote:
> Instead of the floating patches and p-d-ng modifications I sent
> earlier, here are the two complete (so far, well, initial :P) eclasses
> for review.
>
> They are designed as 'mostly' drop-in python-distutils-ng replacement.
Conversion o
On 01-10-2012 17:17:40 +0200, Marien Zwart wrote:
> There used to be a more subtle problem: the python objects you import
> have the path to their source embedded into them, and if you move the
> .pyc/.pyo file around that path would be wrong, confusing some (mostly
> debugging) tools (see http://b
(pardon any awkward formatting, writing from webinterface instead of a
"proper" client. Please yell at me off-list or on irc if this post is
excessively broken.)
> https://bugs.gentoo.org/show_bug.cgi?id=300922
>From that bug:
> - chpathtool does some "simple" heuristic to switch the build EPREF
On Mon, Oct 01, 2012 at 08:36:12AM +0200, Fabian Groffen wrote:
> On 30-09-2012 14:47:17 -0700, Brian Harring wrote:
> > > In the worst case it returns "Bad marshalling data".
> >
> > Examples wanted for this. If this occurs, that's a python bug- one
> > exception... portage (figures). They ins
On 30-09-2012 14:47:17 -0700, Brian Harring wrote:
> > In the worst case it returns "Bad marshalling data".
>
> Examples wanted for this. If this occurs, that's a python bug- one
> exception... portage (figures). They install into a non
> /usr/lib/python* location, meaning the .pyc/.pyo from p
On Sun, Sep 30, 2012 at 10:58:06AM +0200, Fabian Groffen wrote:
> On 30-09-2012 10:31:17 +0200, Pacho Ramos wrote:
> > > > Personally, I usually run:
> > > > - python_clean_py-compile_files -> Clean py-compile files to disable
> > > > byte-compilation allowing us to drop all various ways of doing t
On 09/30/2012 07:12 AM, Fabian Groffen wrote:
> Back then, we found it hurt us (Bad marshalling data) when using
> binpkgs. Not sure if it still does today with Python 2.7. Somehow we
> reached a consensus with the Python maintainer at that time that cache
> stuff shouldn't be in VDB, also becaus
I'm on the list, obviously, so PLEASE stop Cc-ing me!
On 30-09-2012 15:57:16 +0200, Michał Górny wrote:
> > The files are indeed cache, and should be generated on the system that
> > installs the files, not the system that builds them. They are currently
> > outside of VDB. pyc files store the p
On Sat, 29 Sep 2012 22:48:00 +0200
hasufell wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 09/29/2012 08:39 PM, Michał Górny wrote:
> > On Sat, 29 Sep 2012 16:37:15 +0200 Dirkjan Ochtman
> > wrote:
> >
> >> On Sat, Sep 29, 2012 at 4:26 PM, hasufell
> >> wrote:
> >>> That stil
On Sun, 30 Sep 2012 10:58:06 +0200
Fabian Groffen wrote:
> On 30-09-2012 10:31:17 +0200, Pacho Ramos wrote:
> > > > Personally, I usually run:
> > > > - python_clean_py-compile_files -> Clean py-compile files to disable
> > > > byte-compilation allowing us to drop all various ways of doing this t
On 30-09-2012 15:28:47 +0200, Michał Górny wrote:
> > The files are indeed cache, and should be generated on the system that
> > installs the files, not the system that builds them. They are currently
> > outside of VDB. pyc files store the path to the original files, so
> > generating in ${ROOT}
On Sun, 30 Sep 2012 10:58:06 +0200
Fabian Groffen wrote:
> On 30-09-2012 10:31:17 +0200, Pacho Ramos wrote:
> > > > Personally, I usually run:
> > > > - python_clean_py-compile_files -> Clean py-compile files to disable
> > > > byte-compilation allowing us to drop all various ways of doing this t
El dom, 30-09-2012 a las 10:58 +0200, Fabian Groffen escribió:
> On 30-09-2012 10:31:17 +0200, Pacho Ramos wrote:
> > > > Personally, I usually run:
> > > > - python_clean_py-compile_files -> Clean py-compile files to disable
> > > > byte-compilation allowing us to drop all various ways of doing th
On 30-09-2012 10:31:17 +0200, Pacho Ramos wrote:
> > > Personally, I usually run:
> > > - python_clean_py-compile_files -> Clean py-compile files to disable
> > > byte-compilation allowing us to drop all various ways of doing this that
> > > were living in the tree some time ago.
> >
> > Hmm, what
El sáb, 29-09-2012 a las 22:34 +0200, Michał Górny escribió:
> On Sat, 29 Sep 2012 21:20:00 +0200
> Pacho Ramos wrote:
>
> > El sáb, 29-09-2012 a las 20:40 +0200, Michał Górny escribió:
> > > On Sat, 29 Sep 2012 17:45:07 +0200
> > > hasufell wrote:
> > >
> > > > -BEGIN PGP SIGNED MESSAGE---
On 29 September 2012 18:20, Markos Chandras wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 09/29/2012 09:53 AM, Micha? Górny wrote:
>> Hello,
>>
>> Instead of the floating patches and p-d-ng modifications I sent
>> earlier, here are the two complete (so far, well, initial :P)
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/29/2012 08:39 PM, Michał Górny wrote:
> On Sat, 29 Sep 2012 16:37:15 +0200 Dirkjan Ochtman
> wrote:
>
>> On Sat, Sep 29, 2012 at 4:26 PM, hasufell
>> wrote:
>>> That still does not explain the reasons why this work was
>>> initiated.
>>>
>>>
On Sat, 29 Sep 2012 21:20:00 +0200
Pacho Ramos wrote:
> El sáb, 29-09-2012 a las 20:40 +0200, Michał Górny escribió:
> > On Sat, 29 Sep 2012 17:45:07 +0200
> > hasufell wrote:
> >
> > > -BEGIN PGP SIGNED MESSAGE-
> > > Hash: SHA1
> > >
> > > On 09/29/2012 05:37 PM, Ian Stakenvicius wro
On 09/29/2012 12:45 PM, Michał Górny wrote:
> On Sat, 29 Sep 2012 12:00:18 +0200
> Tomáš Chvátal wrote:
>
>> 2012/9/29 Michał Górny :
>>> Hello,
>>>
>>> Instead of the floating patches and p-d-ng modifications I sent
>>> earlier, here are the two complete (so far, well, initial :P) eclasses
>>> f
El sáb, 29-09-2012 a las 20:40 +0200, Michał Górny escribió:
> On Sat, 29 Sep 2012 17:45:07 +0200
> hasufell wrote:
>
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > On 09/29/2012 05:37 PM, Ian Stakenvicius wrote:
> > >
> > > There isn't so much a problem with the current python-d
On Sat, 29 Sep 2012 17:45:07 +0200
hasufell wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 09/29/2012 05:37 PM, Ian Stakenvicius wrote:
> >
> > There isn't so much a problem with the current python-distutils-ng
> > eclass but rather it's to expand it to a more comprehensive
>
On Sat, 29 Sep 2012 16:37:15 +0200
Dirkjan Ochtman wrote:
> On Sat, Sep 29, 2012 at 4:26 PM, hasufell wrote:
> > That still does not explain the reasons why this work was initiated.
> >
> > If there is any way to fix the current eclass, that should be preferred.
>
> I tend to agree. Michał, let
On Sat, 29 Sep 2012 15:49:32 +0200
hasufell wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 09/29/2012 12:49 PM, Michał Górny wrote:
> > On Sat, 29 Sep 2012 11:20:31 +0100 Markos Chandras
> > wrote:
> >
> >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA512
> >>
> >> On 09/29/20
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 29 Sep 2012 17:45:07 +0200
hasufell wrote:
> In that case we are missing 95% of the features of python.eclass.
You say that like it's a bad thing...
Seriously, most of the problem with python.eclass (and several other
problematic eclasses) i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/29/2012 05:50 PM, Ian Stakenvicius wrote:
> On 29/09/12 11:45 AM, hasufell wrote:
>> On 09/29/2012 05:37 PM, Ian Stakenvicius wrote:
>
>>> There isn't so much a problem with the current
>>> python-distutils-ng eclass but rather it's to expand i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 29/09/12 11:45 AM, hasufell wrote:
> On 09/29/2012 05:37 PM, Ian Stakenvicius wrote:
>
>> There isn't so much a problem with the current
>> python-distutils-ng eclass but rather it's to expand it to a more
>> comprehensive replacement for both di
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/29/2012 05:37 PM, Ian Stakenvicius wrote:
>
> There isn't so much a problem with the current python-distutils-ng
> eclass but rather it's to expand it to a more comprehensive
> replacement for both distutils and python eclasses. In order to
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/29/2012 05:37 PM, Ian Stakenvicius wrote:
>
> There isn't so much a problem with the current python-distutils-ng
> eclass but rather it's to expand it to a more comprehensive
> replacement for both distutils and python eclasses. In order to
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 29/09/12 10:26 AM, hasufell wrote:
> On 09/29/2012 04:19 PM, Ian Stakenvicius wrote:
>> On 29/09/12 09:49 AM, hasufell wrote:
>>> On 09/29/2012 12:49 PM, Michał Górny wrote:
On Sat, 29 Sep 2012 11:20:31 +0100 Markos Chandras
wrote:
>
On Sat, Sep 29, 2012 at 4:26 PM, hasufell wrote:
> That still does not explain the reasons why this work was initiated.
>
> If there is any way to fix the current eclass, that should be preferred.
I tend to agree. Michał, let me first say I value the time you have
invested to make the eclasses be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/29/2012 04:19 PM, Ian Stakenvicius wrote:
> On 29/09/12 09:49 AM, hasufell wrote:
>> On 09/29/2012 12:49 PM, Michał Górny wrote:
>>> On Sat, 29 Sep 2012 11:20:31 +0100 Markos Chandras
>>> wrote:
>
-BEGIN PGP SIGNED MESSAGE- Hash:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 29/09/12 09:49 AM, hasufell wrote:
> On 09/29/2012 12:49 PM, Michał Górny wrote:
>> On Sat, 29 Sep 2012 11:20:31 +0100 Markos Chandras
>> wrote:
>
>>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA512
>>>
>>> On 09/29/2012 09:53 AM, Micha? Górny
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/29/2012 12:49 PM, Michał Górny wrote:
> On Sat, 29 Sep 2012 11:20:31 +0100 Markos Chandras
> wrote:
>
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA512
>>
>> On 09/29/2012 09:53 AM, Micha? Górny wrote:
>>> Hello,
>>>
>>> Instead of the float
On Sat, 29 Sep 2012 11:20:31 +0100
Markos Chandras wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 09/29/2012 09:53 AM, Micha? Górny wrote:
> > Hello,
> >
> > Instead of the floating patches and p-d-ng modifications I sent
> > earlier, here are the two complete (so far, well,
On Sat, 29 Sep 2012 12:00:18 +0200
Tomáš Chvátal wrote:
> 2012/9/29 Michał Górny :
> > Hello,
> >
> > Instead of the floating patches and p-d-ng modifications I sent
> > earlier, here are the two complete (so far, well, initial :P) eclasses
> > for review.
> >
> > They are designed as 'mostly' dr
On Sat, 29 Sep 2012 12:00:18 +0200
Tomáš Chvátal wrote:
> 2012/9/29 Michał Górny :
> > Hello,
> >
> > Instead of the floating patches and p-d-ng modifications I sent
> > earlier, here are the two complete (so far, well, initial :P) eclasses
> > for review.
> >
> > They are designed as 'mostly' dr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 09/29/2012 09:53 AM, Micha? Górny wrote:
> Hello,
>
> Instead of the floating patches and p-d-ng modifications I sent
> earlier, here are the two complete (so far, well, initial :P)
> eclasses for review.
>
> They are designed as 'mostly' drop-
2012/9/29 Michał Górny :
> Hello,
>
> Instead of the floating patches and p-d-ng modifications I sent
> earlier, here are the two complete (so far, well, initial :P) eclasses
> for review.
>
> They are designed as 'mostly' drop-in python-distutils-ng replacement.
>
Hi,
the eclasses look pretty, so
Hello,
Instead of the floating patches and p-d-ng modifications I sent
earlier, here are the two complete (so far, well, initial :P) eclasses
for review.
They are designed as 'mostly' drop-in python-distutils-ng replacement.
--
Best regards,
Michał Górny
# Copyright 1999-2012 Gentoo Foundation
48 matches
Mail list logo
