Re: how to get base /usr/bin/env in a package?

[ng0%n0.is@localhost]

Greg Troxel transcribed 884 bytes:
> ng0%n0.is@localhost writes:
> 
> > At build time a package I'm working on is replacing
> > @xENV@ python2.7
> > with the result of which env, resulting in
> > /path/to/env python2.7
> >
> > in pkgsrc this results in:
> >
> > ERROR: /usr/pkg/bin/gnunet-qr:  #!/usr/work/wip/gnunet/work/.tools/bin/env python2.7
> > ERROR: *** The above files still have references to the build directory.
> > ERROR:     This is possibly an error that should be fixed by unwrapping
> > ERROR:     the files or adding missing tools to the package makefile!
> > *** Error code 1
> >
> > I've tried to SUBST_SED, but it always stays at a wrong path.
> >
> > Is there a way to achieve this without changing the upstream Makefile?
> 
> I'm not aware of any.  I am assuming the upstream has the notion of env
> and is trying to find the path to python2.7

Okay, this was a short experiment. I ended up commiting a shell script
which calls the python file to rid ourselves of any env(1) for now.
 
> Are you using REPLACE_PYTHON?  I wonder about teaching it that "@ENV@
> python2.7" should be replaced.

Deliberately I was not, because the whole point of the @ENV@ python2.7
usage was to not get python2.7 in as a dependency (anymore / at build time).
I know that env is considered bad in packaging, but at the time where I
committed the @ENV@ part, discussion wasn't focused on packaging.


Where committed here means with my gnunet hat on, in gnunet git.
I'm still working on wip/gnunet locally because some last parts
are missing (notable a system service file).