On Wed, Mar 14, 2018 at 10:04:21AM +0100, Hartmut Goebel wrote:
> Hi Pjotr,
>
> no offense meant, but I have the impression you did not read my analysis
> and proposals, did you?
No offense taken. I did and do read them, but the analysis is not
exactly accessible for my small brain, especially wh
On 14/03/2018 12:39, Hartmut Goebel wrote:
Am 13.03.2018 um 22:52 schrieb Ludovic Courtès:
2. Use different package names when we know things can be
parallel-installed: “python2” vs. “python” (I’m talking about the
package name, not its version string.) That’s what distros usuall
Ricardo Wurmus writes:
> Hi Ludo,
>
>> Ricardo Wurmus skribis:
>>
>>> I’d like to push this to master in a couple of hours, unless there are
>>> objections.
>>
>> Go for it, thanks a lot!
>
> Pushed to master with commit c4fb2b9f4. Thanks for helping me
> understand this problem!
Commit c4fb2
Ludovic Courtès writes:
> I may well have missed something (sorry about that!), but what are “the
> problems related to how Guix is using PYTHONPATH”?
>
> My first reaction is that Guix is not doing anything special with
> PYTHONPATH, and only defining it as documented by upstream.
The problem
Am 13.03.2018 um 22:52 schrieb Ludovic Courtès:
> 2. Use different package names when we know things can be
> parallel-installed: “python2” vs. “python” (I’m talking about the
> package name, not its version string.) That’s what distros usually
> do, and I think it’s good enough.
Hi Ludo,
> Ricardo Wurmus skribis:
>
>> I’d like to push this to master in a couple of hours, unless there are
>> objections.
>
> Go for it, thanks a lot!
Pushed to master with commit c4fb2b9f4. Thanks for helping me
understand this problem!
--
Ricardo
Hartmut Goebel skribis:
> Am 13.03.2018 um 22:23 schrieb Ludovic Courtès:
>> I may well have missed something (sorry about that!), but what are “the
>> problems related to how Guix is using PYTHONPATH”?
>
> In short:
>
> We are using PYTHONPATH for something it is not meant for: PYTHONPATH is
> N
Hi Ricardo,
Ricardo Wurmus skribis:
> I’d like to push this to master in a couple of hours, unless there are
> objections.
Go for it, thanks a lot!
Ludo’.
Hi Pjotr,
no offense meant, but I have the impression you did not read my analysis
and proposals, did you?
> I propose we patch the interpreter to tell about the Guix paths. It
> probably only needs to be done in one place. They should go after the
> PYTHONPATH as it is done by Python itself, lik
Ludovic Courtès writes:
>> How about a package property that defines a “conflicts?” predicate that
>> takes two packages of the same name and determines (e.g. by checking the
>> major version) if these two packages are conflicting? If no such
>> predicate is provided we assume that packages wit
On Tue, Mar 13, 2018 at 11:02:03PM +0100, Hartmut Goebel wrote:
> Am 13.03.2018 um 22:44 schrieb Pjotr Prins:
> > Another problem is that it does not cover special cases where, for
> > example you compile Python with SSL and without. You don't want them
> > to share user installed libs.
>
> Upstre
11 matches
Mail list logo
