[Bug 4030] New: The Makefiles should not use unconditional assignments for PYTHON

[mercurial-bugs at selenic.com]

http://bz.selenic.com/show_bug.cgi?id=4030

          Priority: normal
            Bug ID: 4030
                CC: mercurial-devel at selenic.com
          Assignee: bugzilla at selenic.com
           Summary: The Makefiles should not use unconditional assignments
                    for PYTHON
          Severity: feature
    Classification: Unclassified
                OS: All
          Reporter: STATUS_ACCESS_DENIED at gmx.net
          Hardware: PC
            Status: UNCONFIRMED
           Version: 2.7.1
         Component: Mercurial
           Product: Mercurial

When attempting to build Mercurial, the assumption is that the Python
interpreter is called "python". Not a big deal.

However, it Python was installed with "make altinstall", that's not the case.
E.g. in my case the interpreter would be python2.7 (an old python2.2 and a
python of version 1.5.1) also exist on this ancient Redhat system.

It looks like the make files are already specific to GNU make, so it would make
sense to use:

  PYTHON?=python

instead of the current:

  PYTHON=python

and do the same for all other variables which make sense to override from the
outside world (i.e. cannot be detected from the interpreter itself).

So instead of editing the make files and then:

  make all

this would have enabled me to not touch the files at all and do:

  make PYTHON=python2.7 all

or:

  PYTHON=python2.7 make all

-- 
You are receiving this mail because:
You are on the CC list for the bug.