>> That "to" looks backwards to me. I expect:
>> link python to your python3
> python3 exists, python does not. So you create python by linking
> it to python3. As Fred says: like cp.
The ln command looked OK to me. I was commenting about the descriptive
text. To me, "to" has an arrow fr
Yo Fred!
On Tue, 1 Apr 2025 16:23:10 -0700 (PDT)
Fred Wright via devel wrote:
> On Tue, 1 Apr 2025, Gary E. Miller via devel wrote:
> > On Mon, 31 Mar 2025 20:52:30 -0700
> > Hal Murray wrote:
> [...]
> > Alternatively, you can create a link to you python3, called python.
> > Like so:
> >
> >
On Tue, 1 Apr 2025, Gary E. Miller via devel wrote:
On Mon, 31 Mar 2025 20:52:30 -0700
Hal Murray wrote:
[...]
Alternatively, you can create a link to you python3, called python.
Like so:
ln -s /usr/bin/python3 /usr/bin/python
That command line doesn't work on FreeBSD or NetBSD
Yeah, *B
Yo Hal!
On Mon, 31 Mar 2025 20:52:30 -0700
Hal Murray wrote:
> > +Alternatively you can link your python3 to python.
> > +`ln -s /usr/bin/python3 /usr/bin/python`
>
> That "to" looks backwards to me. I expect:
> link python to your python3
python3 exists, python does not. So you crea
On Tue, 1 Apr 2025, James Browning via devel wrote:
On Monday, March 31, 2025 8:52:30 PM Pacific Daylight Time Hal Murray via
devel wrote:
buildprep has some python2 cruft. I ignored it.
Should we announce that it no longer works for python 2 and clean it up a
bit?
Don't let Fred, Gary or
On Monday, March 31, 2025 8:52:30 PM Pacific Daylight Time Hal Murray via
devel wrote:
> > +Alternatively you can link your python3 to python.
> > +`ln -s /usr/bin/python3 /usr/bin/python`
>
> That "to" looks backwards to me. I expect:
> link python to your python3
Or, you could symlink "py
