INSTALL.adoc

[Hal Murray]

>> 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 from left to right.


> ... you can create a link to you python3, called python. Like so:

Looks fine.  But second you => your

------

>> That command line doesn't work on FreeBSD or NetBSD
> Yeah, *BSD are weird.  tell me how you do it, and I'll add that as well. 

On FreeBSD
  $ which python3
  /usr/local/bin/python3
  $

On NetBSD
  $ which python3
  /usr/pkg/bin/python3
  $

buildprep says:
  For FreeBSD
     $install python             # python => python3
My attempt at installing NetBSD didn't work and I haven't sorted that out 
yet so I haven't debugged/fixed buildprep for NetBSD yet.

--------

> > Should we fix waf install to do the magic for SELinux?
> Not everyone uses SELinux.  Linus says he hates SELinux.  Doing it for
> all distributiuons would be a can of worms.  I'll stay away from that
> subject. 

Fedora is the only system where I've encountered it.

I was thinking of running the extra steps only if SELinux was active.  
There is a program to test that.  I've forgotten the name.  So we would 
have to test for the program being installed and then test its result.  Or 
just test for it being installed in case it is turned off while waf 
install is run and gets turned back on later.



-- 
These are my opinions.  I hate spam.