On Sat, 31 Aug 2019, Blair Zajac wrote:
The problem could be scons. It looks like
https://github.com/mongodb/mongo/blob/r4.2.0/SConstruct
requires Python 3.5 but Scons runs against Python 2.7:
$ head /opt/local/bin/scons
The problem could be scons. It looks like
https://github.com/mongodb/mongo/blob/r4.2.0/SConstruct
requires Python 3.5 but Scons runs against Python 2.7:
$ head /opt/local/bin/scons
#!/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7
So try changing
Dang, forgot the link:
[1] https://github.com/mongodb/mongo/blob/master/docs/building.md
* Blair Zajac:
> Is this port only for you and you’ll not commit it to the Git repo?
As of now, I am only trying that particular build for myself.
> Which package is this?
I am trying to build MongoDB 4.2.0 by modifying the existing Portfile
(that's version 4.0.12). According to the docs[1],
> On Aug 31, 2019, at 7:30 PM, Ralph Seichter wrote:
>
>> You’ll want to avoid the PATH approach as it requires that
>> ${prefix}/bin/python be symlinked to a Python 3.x, which isn’t always
>> the case.
>
> Not always, but it is for me:
>
> $ ls -dl /opt/local/bin/python
> lrwxr-xr-x 1 root
> On Aug 31, 2019, at 5:30 PM, Ralph Seichter wrote:
>
> * Blair Zajac:
>
>> You’ll want to avoid the PATH approach as it requires that
>> ${prefix}/bin/python be symlinked to a Python 3.x, which isn’t always
>> the case.
>
> Not always, but it is for me:
>
> $ ls -dl
* Blair Zajac:
> You’ll want to avoid the PATH approach as it requires that
> ${prefix}/bin/python be symlinked to a Python 3.x, which isn’t always
> the case.
Not always, but it is for me:
$ ls -dl /opt/local/bin/python
lrwxr-xr-x 1 root admin24B 11 Jul 16:50 /opt/local/bin/python@
You’ll want to avoid the PATH approach as it requires that ${prefix}/bin/python
be symlinked to a Python 3.x, which isn’t always the case. I have
${prefix}/bin/python symlinked to Python 2.7.
Instead tell it to use ${prefix}/bin/python3.7. You’ll have to poke into the
project to see how to
I am wrestling with a port that requires Python >=3.5 to build, and
Python 3.7 is the chosen one:
$ which python
/opt/local/bin/python
$ python --version
Python 3.7.4
Looks good to me. However, the build log shows the following:
:info:build Python 3.5 or greater required, but you have
Bjarne,
Thanks for adding all those missing sub-ports!
I had seen many of these in the FreeBSD ports on my servers (I currently only
use certbot under FreeBSD, as I no longer maintain any macOS based servers that
are exposed to the internet).
With some minor tweaks, I’ll fold this into the
> On Aug 31, 2019, at 11:15 AM, Chris Jones wrote:
>
>
>
>> On 31 Aug 2019, at 7:12 pm, Blair Zajac wrote:
>>
>> Hi,
>>
>> Ok, I get that.
>>
>> Can we come up with a solution that works for you and for people that want
>> to see all outdated ports they have installed easily?
>>
>>
> On 31 Aug 2019, at 7:12 pm, Blair Zajac wrote:
>
> Hi,
>
> Ok, I get that.
>
> Can we come up with a solution that works for you and for people that want to
> see all outdated ports they have installed easily?
>
> How about doing this?
>
> $ port live maintainer:cjones | uniq -f 1
Bjarne D Mathiesen wrote:
>
> Presently, I'm trying to modify py-acme & cerbot to use git instead .
> These two ports are among the for me mission critical ones.
> And I spent several days getting certbot to integrate with my dns
> service. ( I have to use "dns-01 challenge" because I use
Hi,
Ok, I get that.
Can we come up with a solution that works for you and for people that want to
see all outdated ports they have installed easily?
How about doing this?
$ port live maintainer:cjones | uniq -f 1
Would that work for you? It prints only the first main port reports.
Blair
>
Hi,
I use
port live maintainer:cjones
For that. For the py ports I maintain I do not want the above to give multiple
reports for each version supported. Hence the livecheck none for these, so only
the main stub port reports back.
Chris
> On 31 Aug 2019, at 7:02 pm, Blair Zajac wrote:
>
>
Yes, however, it’s not as convenient as seeing what ports you have that have
new upstream versions. I would rather take more computing time and resources
then my time manually doing `port livecheck py-virtualenv` and the other ones.
My time is much more valuable than 4 times the number of HTTP
It is intentional that the version specific py ports have livecheck none. The
idea is you don’t need every one of the versions performing the check, only the
non versioned port.
> On 31 Aug 2019, at 5:50 pm, Blair Zajac wrote:
>
> I care about such ports, e.g. py37-tensorflow and
I care about such ports, e.g. py37-tensorflow and py37-virtualenv, so I would
have that in requested. So that appears to not directly solve the issue.
> On Aug 31, 2019, at 9:16 AM, Jeremy Lavergne wrote:
>
> As an alternative or workaround, would narrowing to `port livecheck
> requested` be
oh no, bjarnehas to happen.!
whatever issue might remain, we will fix.
this will greatly simplify things for older systems, and keep them supported
longer. Trying to build c++11 w clang against the gcc headers is driving me
batty and causing way too much wasted effort...
Ken
Joshua Root wrote:
> I think we're pretty close to being ready to make a new stable branch
> and tag a beta. Clemens is going to make one more change related to
> Xcode checking; are there any other changes that really need to go in
> before the beta?
⛔️
Presently, I'm of the opinion that the
As an alternative or workaround, would narrowing to `port livecheck
requested` be useful for you?
On 8/31/19 11:58 AM, Blair Zajac wrote:
Hi all,
It appears a number of ports, particularly py-* ports, use “livecheck.type
none”. I find running ‘port livecheck installed’ a handy way to see if
Hi all,
It appears a number of ports, particularly py-* ports, use “livecheck.type
none”. I find running ‘port livecheck installed’ a handy way to see if any of
the ports I care about have an update, however, this doesn’t work for the py-*
ones.
Can something be changed to support this? Would
A description of the "build.dir" & "configure.dir" keywords are missing
I only discovered these keywords by accident by looking in a Portfile
for help with exactly these issues : changing into a directory before a
python install
Possible description :
build.dir
Changes into this directory before
23 matches
Mail list logo
