pkgsrc-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: [PATCH] fix installation of wip/py-whel with differing pythons

Am Tue, 26 Jan 2016 00:03:09 +0100
schrieb Thomas Klausner <>:

> This is fine. You can go one step further and add an ALTERNATIVES file
> so that bin/wheel exists if you have the pkg_alternatives package
> installed.

Actually my cargo-culting starting with ALTERNATIVES. But in my
application, installing both Python 2.7 and 3.4 (3.5) toolchains, it
would be dangerous to have any default binary without version suffix,
because of surprises.

What I am wondering about: Should it be wheel-X.Y or wheelX.Y? I see
inconsistent application of the dash in python-specific commands. So I
guess one has to live with that?

> There are lots of examples for them in pkgsrc, and you already have

Yeah, I figure it would work by simply adding that ALTERNATIVES that I
had briefly (non-functional). But as I do not use pkg_alternatives, I
would not test that naturally, so it is perhaps better someone else
does that additional change.

I'm now busy figuring out why, again, my patch to use a certificate
bundle for curl with builtin openssl instead of a cert dir didn't
result in working https … that will be another topic.

I hope I will have more time to more nicely interact with pkgsrc
upstream sometime, but for now I hope I can be a bit helpful with my
hackish incomplete patches sent from time to time.

Alrighty then,


Dr. Thomas Orgis
Universität Hamburg
RRZ / Zentrale Dienste / HPC
Schlüterstr. 70
20146 Hamburg
Tel.: 040/42838 8826
Fax: 040/428 38 6270

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Home | Main Index | Thread Index | Old Index