Re: bin-install fails for non-default python versions

[Greg Troxel <gdt%lexort.com@localhost>]

Greg Troxel <gdt%lexort.com@localhost> writes:

> ===> Binary install for py313-virtualenv-[0-9]*
> => Becoming ``root'' to make su-do-bin-install (sudo)
> PKGWILDCARD <py312-virtualenv-[0-9]*>
> ERROR: py312-virtualenv-20.28.0 is already installed - perhaps an older version?
> ERROR: If so, you may wish to ``pkg_delete py312-virtualenv-20.28.0'' and install
> ERROR: this package again by ``/usr/bin/make bin-install'' to upgrade it properly.
> *** Error code 1
>
> It seems like somehow the required for py313- is being lost and it's
> flipping back to py312.  (PKGWILDCARD line is just echo.)

I got an offlist comment that this works on when running as root or in
pbulk.  (I'm not sure about pbulk, as I thought it installed what was
needed, rather than letting the package use bin-install.)

That was a huge clue, and I quickly confirmed that the right package is
looked for if either:

  SU_CMD is default and su is used
  running as root and hence no su/sudo of any kind

I then changed SU_CMD's use of sudo to add -E to preserve the
environment.  (A few year's ago, sudo started clearing the environment
except for a limited set of variables.)

With that, the right package was looked for and a build of a non-default
package seems ok.

The incanation is:

SU_CMD=                 sudo -E /bin/sh -c