On 2018-6-3 07:28 , Mojca Miklavec wrote:
> The whole idea of the graveyard was to help users migrate to a newer
> version automatically, but in case of python it doesn't really serve
> the purpose if ports get moved to the graveyard at random times (ok,
> it makes sure that ports don't end up
Ryan,
> On Jun 2, 2018, at 5:16 PM, Ryan Schmidt wrote:
>
>
> On Jun 2, 2018, at 16:51, Marius Schamschula wrote:
>
>> Marius Schamschula (Schamschula) pushed a commit to branch master
>> in repository macports-ports.
>>
>>
>>
On Jun 2, 2018, at 16:51, Marius Schamschula wrote:
> Marius Schamschula (Schamschula) pushed a commit to branch master
> in repository macports-ports.
>
>
> https://github.com/macports/macports-ports/commit/4c13d30353d2d95d746769aad50070aebdb4b688
>
> The following commit(s) were added to
Hi,
Recently a PR has been merged which put a py35 subport into a graveyard.
I just wanted to say that we should first focus our efforts into:
* Getting entirely rid of python 2.6 and python3.3 and lower, starting
with regular ports like vim which still ships with python26 and
python33 variants
On 2018-6-2 17:36 , Andrew Moore wrote:
> On Jun 1, 2018, at 7:36 PM, Joshua Root wrote:
>>
>> Please test the changes that are now on the release-2.5 branch. Are
>> there any other things that need to be fixed for a 2.5.1 release in the
>> very near future?
>
> Looks good, so far. SuiteSparse
On Jun 1, 2018, at 7:36 PM, Joshua Root wrote:
>
> Please test the changes that are now on the release-2.5 branch. Are
> there any other things that need to be fixed for a 2.5.1 release in the
> very near future?
Looks good, so far. SuiteSparse is happy.
Added ` configure.cxx_stdlib
