Installing a Python wheel (whl) file using a port

Hi, I’m trying to create a port for TensorFlow and I have already accumulated quite a number of doubts in just a couple of hours I've been working on it. First of all, I realised (late) that TensorFlow (and some of its dependencies) is built as a wheel package (a .whl file), and as such it gets

Re: Installing a Python wheel (whl) file using a port - Tensorflow

. Marius was taking this on a few months ago as well, so might have some thoughts. Ken On 2017-12-18, at 1:52 PM, Enrico Maria Crisostomo wrote: Hi, I’m trying to create a port for TensorFlow and I have already accumulated quite a number of doubts in just a couple of hours I've been working

Re: Installing a Python wheel (whl) file using a port - Tensorflow

: https://github.com/Homebrew/homebrew-core/blob/master/Formula/libtensorflow.rb On 2017-12-18, at 2:09 PM, Enrico Maria Crisostomo wrote: Thanks Ken. Actually I checked brew and they haven't got a formula for TensorFlow (at least at the moment). On 18 December 2017 at 22:57:42, Cunningham Ken

Re: request for port create command, to build a portfile from a URL

md5${CHECKSUM_MD5} rmd160 ${CHECKSUM_RMD160} sha256 ${CHECKSUM_SHA256} size ${CHECKSUM_SIZE} livecheck.url \${github.homepage}/releases/latest > On 7 Mar 2018, at 10:23, Enrico Maria Crisostomo > <enr

Re: request for port create command, to build a portfile from a URL

> On 11 Mar 2018, at 16:40, Rainer Müller <rai...@macports.org> wrote: > > On 2018-03-09 20:22, Enrico Maria Crisostomo wrote: >> I pushed to GitHub a skeleton of the idea: >> >>https://github.com/emcrisostomo/macports-utils >> >> I've mov

Re: request for port create command, to build a portfile from a URL

> On 12 Mar 2018, at 08:28, Ryan Schmidt <ryandes...@macports.org> wrote: > > > On Mar 9, 2018, at 13:22, Enrico Maria Crisostomo wrote: > >> I pushed to GitHub a skeleton of the idea: >> >> https://github.com/emcrisostomo/macports-utils >>

Re: request for port create command, to build a portfile from a URL

Thanks Ryan for the explanation. > On 7 Mar 2018, at 19:51, Ryan Schmidt <ryandes...@macports.org> wrote: > > > On Mar 7, 2018, at 07:32, Rainer Müller wrote: > >> On 2018-03-07 11:32, Enrico Maria Crisostomo wrote: >>> This is a little bit offtopic

Re: request for port create command, to build a portfile from a URL

This is a little bit offtopic IMHO, anyway: I found surprising too that the github portgroup was not documented, given the high percentage of software that I build out of github repositories, and that's why I recently contributed the documentation of the github portgroup:

Re: Include file search path problem building py-grpcio with setuptools

> On 2 Apr 2018, at 19:50, Joshua Root <j...@macports.org> wrote: > > On 2018-4-3 02:12 , Enrico Maria Crisostomo wrote: >> How is the compiler include file search path set up in this case? The >> /opt/local/include/openssl path should come from MacPorts, but I do

port version reports 2.4.2 when built from tag v2.4.3

Hi, I've just created a new installation of macports-base from tag v2.4.3 following the instructions in the documentation (basically git checkout v2.4.3, ./configure ..., make and make install) and I've just noticed that `port` reports 2.4.2: % which port /opt/macports-2.4.3/bin/port

Re: port version reports 2.4.2 when built from tag v2.4.3

> On 11 Apr 2018, at 14:22, Rainer Müller <rai...@macports.org> wrote: > > On 2018-04-11 10:52, Enrico Maria Crisostomo wrote: >> I've just created a new installation of macports-base from tag v2.4.3 >> following the instructions in the documentation (basically git check

Re: port version reports 2.4.2 when built from tag v2.4.3

ean the repo between the builds, the problem does not happen. Cheers, -- Enrico > On 11 Apr 2018, at 15:32, Joshua Root <j...@macports.org> wrote: > > On 2018-4-11 23:27 , Enrico Maria Crisostomo wrote: >> Thanks Rainer, >> >> I can't check it but as I said in my p

Re: port version reports 2.4.2 when built from tag v2.4.3

; On 11 Apr 2018, at 14:17, Joshua Root <j...@macports.org> wrote: > > On 2018-4-11 18:52 , Enrico Maria Crisostomo wrote: >> Hi, >> >> I've just created a new installation of macports-base from tag v2.4.3 >> following the instructions in the documentatio

Re: port version reports 2.4.2 when built from tag v2.4.3

ath should have /opt/local/bin first. > > On Wed, Apr 11, 2018 at 06:48 Enrico Maria Crisostomo > <enrico.m.crisost...@gmail.com> wrote: > Well, I replicated it: > > * Clean the repo (e.g.: git clean -xfd) > * git checkout v2.4.2 > * build and install 2.4.2: >

Re: port version reports 2.4.2 when built from tag v2.4.3

Ok, now I'm sufficiently curious as to dig deeper and replicate what I think the sequence of events were. > On 11 Apr 2018, at 15:32, Joshua Root <j...@macports.org> wrote: > > On 2018-4-11 23:27 , Enrico Maria Crisostomo wrote: >> Thanks Rainer, >> >> I c

Re: port version reports 2.4.2 when built from tag v2.4.3

> On 12 Apr 2018, at 02:30, Ryan Schmidt <ryandes...@macports.org> wrote: > > > On Apr 11, 2018, at 08:48, Enrico Maria Crisostomo wrote: > >> Well, I replicated it: >> >> * Clean the repo (e.g.: git clean -xfd) >> * git checkout v2.4.2 >>

Re: port version reports 2.4.2 when built from tag v2.4.3

gt; wrote: > > > On Apr 12, 2018, at 03:39, Enrico Maria Crisostomo wrote: > >> On 12 Apr 2018, at 02:30, Ryan Schmidt wrote: >> >>> On Apr 11, 2018, at 08:48, Enrico Maria Crisostomo wrote: >>> >>>> Well, I replicated it: >>>> >>&

Re: port version reports 2.4.2 when built from tag v2.4.3

, as I said in a previous mail. Cheers, -- Enrico > On 13 Apr 2018, at 22:28, Enrico Maria Crisostomo > <enrico.m.crisost...@gmail.com> wrote: > > Ryan, > > Unless there's something I'm not understanding, in which case I apologise for > the noise, I don't think my sh

Re: port version reports 2.4.2 when built from tag v2.4.3

> On 13 Apr 2018, at 23:55, Joshua Root <j...@macports.org> wrote: > > On 2018-4-14 07:30 , Enrico Maria Crisostomo wrote: >> I think I found the culprit: >> >>% strings /opt/macports-2.4.3-dirty/libexec/macports/lib/libtcl8.5.dylib >> | grep 2\\

Re: pypi livecheck not working any longer

> On 17 Apr 2018, at 01:08, Ryan Schmidt <ryandes...@macports.org> wrote: > > > On Apr 16, 2018, at 15:53, Enrico Maria Crisostomo wrote: > >> I was running livecheck a few minutes ago on a bunch of ports of mine and I >> started getting the same error on all

pypi livecheck not working any longer

Hi all, I was running livecheck a few minutes ago on a bunch of ports of mine and I started getting the same error on all the pythons ones: Error: cannot check if [portname] was updated (regex didn't match) All the ports use pypi so, after a quick search I think livecheck is using by

Include file search path problem building py-grpcio with setuptools

Hi, When building py-grpcio I'm getting this error: :notice:build ---> Building py27-grpcio :debug:build Executing proc-pre-org.macports.build-build-0 :debug:build Executing org.macports.build (py27-grpcio) :debug:build Environment: :debug:build CC='/usr/bin/clang' :debug:build

Re: Python ports: should we use wheel files?

> On 2 Apr 2018, at 08:35, Joshua Root wrote: > > Good summary from Rainer, which covers most of what I was going to say. > > On 2018-4-1 12:53 , Rainer Müller wrote: >> I see two reasons why python modules need natively compiled binary files: >> >> a) for performance >> b)

Python ports: should we use wheel files?

Hi all, While updating the py-tensorflow port to 1.6.0 I started to think about this question: we shortly discussed about it on the corresponding PR (https://github.com/macports/macports-ports/pull/1499) and decided to bring it up in the mailing list. Safe harbour statement: I'm a Python

python package installed with setuptools: fixing permission of the PKG-INFO file

Hi all, I'm working on fixing a `py-tensorflow` port issue (https://trac.macports.org/ticket/55972) and I've found the following problem when building `py-protobuf3`: ---> Building py36-protobuf3 Error: Failed to build py36-protobuf3: command execution failed The log shows the

Re: python package installed with setuptools: fixing permission of the PKG-INFO file

> On 23 Mar 2018, at 11:37, Mojca Miklavec <mo...@macports.org> wrote: > > On 23 March 2018 at 11:35, Enrico Maria Crisostomo wrote: >> On 23 Mar 2018, at 11:06, Mojca Miklavec wrote: >>> >>> I would say this in an upstream issue that should be repor

Re: python package installed with setuptools: fixing permission of the PKG-INFO file

On 23 Mar 2018, at 11:06, Mojca Miklavec <mo...@macports.org> wrote: > > On 23 March 2018 at 10:28, Enrico Maria Crisostomo > <enrico.m.crisost...@gmail.com> wrote: >> Hi all, >> >> I'm working on fixing a `py-tensorflow` port issue >> (https://t

python portgroup best practices for apps (and how to migrate a port from module to app)

Hi all, Yesterday a brief discussion started in macports-ports PR #6496 where we were arguing about python apps best practices. Basically, a port update submission was made to add variants to a port (httpie) to support additional python

Re: Buildbot hardware (was: Re: Framing the MacPorts discussion)

not be relaxed. * I volunteered because I thought they were needed: I love MacPorts, and I want it to thrive. Bye, Enrico From: Ben Greenfield Date: Friday, 21 May 2021 at 13:26 To: Ryan Schmidt Cc: Andrew Janke , Enrico Maria Crisostomo , MacPorts Developers Subject: Re: Buildbot hardware

Re: Framing the MacPorts discussion

Hi all, I've got an iMac Pro in my LAN with 16 vCores and 64GB or RAM which is quite often idle. I'm not privy with how our build system work, but if we could get to a point where agents can be added, stopped, throttled, trusted members of our community could volunteer the computational power

Re: libgcc11 on macOS monterey

Hi Brian, My system just finished building it and I had no issues: libgcc11 @11.2.0_1 Have you updated your port installation and your ports tree? There have been quite a lot of updates in the last few hours (even though I'm not aware of anything that would break this