msarahan on csoja-patch-1
msarahan on master
Update issue template add code… Merge pull request #3853 from c… (compare)
csoja on csoja-patch-1
Update issue template add code… (compare)
ORIGINpaths, which it is ok with later, but the but not
runpath, hence the error.
patchelfdoesn’t seem to make any distinction between the two, so calling
patchelf --force-rpath --set-rpath …will replace the existing
RUNPATHon my binary with another
RUNPATH- maybe that’s what it is supposed to do
rpathand I’m set...
on another topic, is there a way to disentagle a recipe called
package with an output of the same name?
I would like to have a recipe where the top-level build gets split up into subpackages using
outputs/files, where one output has the same name as the top-level package. That output’s
requirements are a proper subset of the overall build requirements, but
conda-build seems to preferentially select the
requirements list over the top-level list when building the environments to use for the top-level build stage. Is that bug, or am I just using
conda-build and outputs incorrectly?
#!/usr/bin/env python # EASY-INSTALL-ENTRY-SCRIPT: 'pytest==3.6.2','console_scripts','pytest' __requires__ = 'pytest==3.6.2' import re import sys from pkg_resources import load_entry_point if __name__ == '__main__': sys.argv = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv) sys.exit( load_entry_point('pytest==3.6.2', 'console_scripts', 'pytest')() )
/usr/bin/envinstead of the full host prefix here?
/usr/bin/envinvoking SIP and breaking everything