OK, I see.
Maybe though you could learn from what the macports port does, and try and
replicate it. Note it does install stuff to ${prefix}/bin, as you want. e.g.> port contents py37-awscli <snip> /opt/local/bin/aws-3.7 /opt/local/bin/aws.cmd-3.7 /opt/local/bin/aws_bash_completer-3.7 /opt/local/bin/aws_completer-3.7 /opt/local/bin/aws_zsh_completer.sh-3.7 <snip> so you should take a look into how it achieves that. sudo port -s -d install py37-awscli will force a build from source, with full debug output. Another possibility is you clone the port and make a new ‘devel’ version of it, that takes the nightly snapshot you want instead of the released version, but uses the rest of the infrastructure just the same. Chris > On 2 Dec 2019, at 9:11 pm, Forrest <for...@forrie.com> wrote: > > I have a need to run the latest GIT of the aws-cli, so while the port is > there, I need to be able to compile and install the nightly code updates for > testing. > > So I am building aws-cli from the GIT repository. > > > Thanks. > > > On 12/2/19 3:07 PM, Christopher Jones wrote: >> >> OK. >> >> So when you say build from source, do you mean using MacPorts port for this, >> or are you building directly yourself (and if the later, any reason why you >> are not using the port ?) >> >> https://github.com/macports/macports-ports/blob/master/python/py-awscli/Portfile >> >> <https://github.com/macports/macports-ports/blob/master/python/py-awscli/Portfile> >> >> >>> crjoberon ~ > port search awscli >>> awscli_select @0.1 (python, sysutils) >>> common files for selecting default awscli version >>> >>> py-awscli @1.16.292 (python) >>> Universal Command Line Environment for AWS. >>> >>> py27-awscli @1.16.292 (python) >>> Universal Command Line Environment for AWS. >>> >>> py35-awscli @1.16.292 (python) >>> Universal Command Line Environment for AWS. >>> >>> py36-awscli @1.16.292 (python) >>> Universal Command Line Environment for AWS. >>> >>> py37-awscli @1.16.292 (python) >>> Universal Command Line Environment for AWS. >> >> >> >>> On 2 Dec 2019, at 8:43 pm, Forrest <forrie@forr >> >>> ie.com <http://ie.com/>> wrote: >>> >>> The /usr/bin/python installs the executable into /usr/local/bin. I'd be >>> fine if the Macports installed it in /opt/local/bin -- this makes me >>> believe there is a config directive I'm missing somewhere. >>> >>> >>> >>> On 12/2/19 2:38 PM, Christopher Jones wrote: >>>> When you say " vs /usr/bin/python that does the right thing and places the >>>> commands in proper places “ where exactly are you referring to ? Where >>>> exactly do you want the macports provided python to install things to ? >>>> >>>>> On 2 Dec 2019, at 7:50 pm, Forrest <for...@forrie.com >>>>> <mailto:for...@forrie.com>> wrote: >>>>> >>>>> I'm new to Python and I'm trying to figure out why, for example, when I >>>>> install aws-cli (from source) using Macports, it doesn't install properly >>>>> vs /usr/bin/python that does the right thing and places the commands in >>>>> proper places. When I run "/opt/local/bin/python setup.py install" it >>>>> ends up buried in directories under the Macports directory structure, >>>>> which isn't usable. Maybe I am missing some ENV variables? >>>>> >>>>> >>>>> >>>>> F >>>>> >>> >> >
smime.p7s
Description: S/MIME cryptographic signature
