On Monday June 03 2019 05:39:12 Ryan Schmidt wrote:
>Sure. I did something like that recently for gettext,
Thanks!
R.
On Jun 3, 2019, at 04:20, René J.V. Bertin wrote:
>
> Would it be possible (and acceptable) to prevent the kind of build failure
> we're talking about here by setting up a temporary symlink to a sanctioned
> python interpreter in a build-specific tmp directory and prepend that
> directory to
Hi,
Would it be possible (and acceptable) to prevent the kind of build failure
we're talking about here by setting up a temporary symlink to a sanctioned
python interpreter in a build-specific tmp directory and prepend that directory
to the configure/build/destroot paths (if there isn't one yet
On 2019-6-3 07:14 , Christopher Jones wrote:
> For me, we should allow ‘port select python’ to select a 3.x version,
> but at the moment issue a warning to the user if they do this they might
> have problems.
Which is what the ticket is asking for.
> Also none of what a user might or might not do
Hi,
>> However, the person who reported the error to me claimed he only used `port
>> select` and didn't create the symlink himself. I didn't push him to know how
>> nor did I try myself, but if indeed `port select` allows this calling it a
>> "user error" is a bit unjust. You cannot expect eve
#x27;t a good idea for the user
to do this.
On Jun 2, 2019, at 13:49, René J.V. Bertin wrote:
> Ryan Schmidt wrote on 20190602::10:59:47 re: "Re: `port select python` and
> qtwebengine"
>> As a side note, as I understand it, it is a user error to make "python" a
>&g
On 2019-6-3 01:59 , Ryan Schmidt wrote:
> As a side note, as I understand it, it is a user error to make "python" a
> symlink to Python 3; it should always be Python 2. Going forward, use a
> "python2" symlink for Python 2 and use a "python3" symlink for Python 3.
>
> https://trac.macports.org/t
On Jun 2, 2019, at 10:03, René J.V. Bertinwrote:
> I just learned that the QtWebEngine build process has a hard dependency on
> python 2 and cannot be configured to use a specific python interpreter
> exclusively. In other words, it fails if a user apparently used `port select
> python` to m
Hi,
The behaviour of any given portfile should never depend on whatever ‘port
select’ choices a user may have made. The base changes you describe below seem
and overly complex way to solve the problem in general. If a build requires a
given python version, but provides no options to control how
Hi,
I just learned that the QtWebEngine build process has a hard dependency on
python 2 and cannot be configured to use a specific python interpreter
exclusively. In other words, it fails if a user apparently used `port select
python` to make a python 3 interpreter the default one.
I think "ba
10 matches
Mail list logo
