Yo Richard!
On Mon, 15 Jan 2018 16:14:33 -0600
Richard Laager via devel wrote:
> On 01/15/2018 03:59 PM, Gary E. Miller via devel wrote:
> > On Mon, 15 Jan 2018 15:47:02 -0600
> > Richard Laager wrote:
> >
> >> On 01/15/2018 03:39 PM, Gary E. Miller via devel wrote:
> >>> My understanding
On 01/15/2018 03:59 PM, Gary E. Miller via devel wrote:
> On Mon, 15 Jan 2018 15:47:02 -0600
> Richard Laager wrote:
>
>> On 01/15/2018 03:39 PM, Gary E. Miller via devel wrote:
>>> My understanding is that /usr/local/lib*/python*/dist-packages
>>> should NEVER exit. dist-packages is only for Deb
Yo Richard!
On Mon, 15 Jan 2018 15:47:02 -0600
Richard Laager wrote:
> On 01/15/2018 03:39 PM, Gary E. Miller via devel wrote:
> > My understanding is that /usr/local/lib*/python*/dist-packages
> > should NEVER exit. dist-packages is only for Debian distro use, and
> > the distro stuff is always
On 01/15/2018 03:39 PM, Gary E. Miller via devel wrote:
> My understanding is that /usr/local/lib*/python*/dist-packages should
> NEVER exit. dist-packages is only for Debian distro use, and the distro
> stuff is always in /usr, not /usr/local/
This is incorrect.
I think you're basing a lot of th
Yo Hal!
On Sun, 14 Jan 2018 22:28:37 -0800
Hal Murray via devel wrote:
> > Assuming this is a newly-installed system, /usr/local/lib/python2.7/
> > dist-packages does not exist. Since it does not exist, it does not
> > show up in sys.path.
My understanding is that /usr/local/lib*/python*/dis
On 01/15/2018 12:28 AM, Hal Murray wrote:
> Is there a reasonable way to tell if /usr/local/whatever would be on sys.path
> if it existed?
I don't know enough to say.
> I assume touching the directory would work.
Yes.
--
Richard
___
devel mailing li
> Assuming this is a newly-installed system, /usr/local/lib/python2.7/
> dist-packages does not exist. Since it does not exist, it does not show up
> in sys.path.
Thanks. That's the example I was looking for.
There is another example based on that which is when the user doesn't
actually inten
On 01/14/2018 10:09 PM, Hal Murray wrote:
>> 1) Does configure bail if installing the python libs might not work? No.
>
>> I think #1 always has to be no. Otherwise, you'll break tons of working
>> setups, including but not limited to package builds.
>
> Could you please say more.
>
> I'm assu
On 01/12/2018 09:44 PM, Richard Laager wrote:
> 1. Determine the directory:
>$ python -c 'import sys ; print(sys.path)[1]'
>For example:
>/usr/lib/python2.7
I was incorrect here. Use this instead:
1. Determine the directory:
$ python -c 'from distutils import sysconfig ;
print(sys
Thanks.
> 1) Does configure bail if installing the python libs might not work? No.
> I think #1 always has to be no. Otherwise, you'll break tons of working
> setups, including but not limited to package builds.
Could you please say more.
I'm assuming that PYTHONPATH or xxx.pth would fix the
On 01/12/2018 03:45 PM, Hal Murray via devel wrote:
> What is the current status?
ntpsec follows upstream waf's behavior. It no longer violates --prefix.
> Does configure bail if installing the python libs in /usr/local/ isn't going
> to work?
At configure time, waf cannot tell that it *will no
Yo Hal!
On Fri, 12 Jan 2018 17:43:46 -0800
Hal Murray via devel wrote:
> > Yup. Do we know if this can fail silently?
>
> I tried it. It's not silent.
Cool.
> >> What I really meant was won't work after installed.
> > Well, that would be a hard question to answer. Should we restart
> >
Gary said.
> Yup. Do we know if this can fail silently?
I tried it. It's not silent.
Waf: Leaving directory `/home/murray/ntpsec/play/hgm/main'
Build failed
Traceback (most recent call last):
File "/home/murray/ntpsec/play/.waf-1.9.14-d7f6128a2aa20a656027b134f0b4f4a6/
waflib/Task.py", line 1
Yo Hal!
On Fri, 12 Jan 2018 17:14:42 -0800
Hal Murray via devel wrote:
> >> Does configure bail if installing the python libs in
> >> /usr/local/ isn't going to work?
>
> Poor choice of words on my part. "going to work" is ambiguous. One
> possibility is that the install won't work, maybe
>> Does configure bail if installing the python libs in
>> /usr/local/ isn't going to work?
Poor choice of words on my part. "going to work" is ambiguous. One
possibility is that the install won't work, maybe because a directory doesn't
exist. But it should be able to create directories so m
Yo Hal!
On Fri, 12 Jan 2018 13:45:03 -0800
Hal Murray via devel wrote:
> What is the current status?
Dunno, I've been on the road.
> Does configure bail if installing the python libs in /usr/local/
> isn't going to work?
Why limit it to /usr/local? If install can't install something where
th
What is the current status?
Does configure bail if installing the python libs in /usr/local/ isn't going
to work?
Do we have a good writeup for the PYTHONPATH and/or .pth solutions?
--
These are my opinions. I hate spam.
___
devel mailing list
17 matches
Mail list logo
