Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
An example for a current problem; the file downloaded can have a trivial name such as install.sh and collide with similar files (the rm is especially problematic here I think). This is why tem...
Answer
#2: Post edited
by
Peter Taylor
·
2021-03-21T22:21:11Z (over 3 years ago)
- > An example for a current problem; the file downloaded can have a trivial name such as install.sh and collide with similar files (the rm is especially problematic here I think).
- This is why `tempfile` exists.
- FILENAME=`tempfile`
cd ${HOME} &&- wget -O ${FILENAME} https://raw.githubusercontent.com/<username>/<project>/<branch>/<path>/<file> &&
- source ${FILENAME} &&
- rm ${FILENAME}
If you really want the temp file to be in `~`, you can change the invocation to `tempfile -d ${HOME}`.
- > An example for a current problem; the file downloaded can have a trivial name such as install.sh and collide with similar files (the rm is especially problematic here I think).
- This is why `tempfile` exists.
- FILENAME=`tempfile`
- cd DESTINATION &&
- wget -O ${FILENAME} https://raw.githubusercontent.com/<username>/<project>/<branch>/<path>/<file> &&
- source ${FILENAME} &&
- rm ${FILENAME}
- If you really want the temp file to be in `DESTINATION`, you can change the invocation to `tempfile -d DESTINATION`.
#1: Initial revision
by
Peter Taylor
·
2021-03-20T19:52:54Z (over 3 years ago)
> An example for a current problem; the file downloaded can have a trivial name such as install.sh and collide with similar files (the rm is especially problematic here I think).
This is why `tempfile` exists.
FILENAME=`tempfile`
cd ${HOME} &&
wget -O ${FILENAME} https://raw.githubusercontent.com/<username>/<project>/<branch>/<path>/<file> &&
source ${FILENAME} &&
rm ${FILENAME}
If you really want the temp file to be in `~`, you can change the invocation to `tempfile -d ${HOME}`.