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.

Review Suggested Edit

You can't approve or reject suggested edits because you haven't yet earned the Edit Posts ability.

> 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`.~~

> 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 DESTIONATION &&
wget -O ${FILENAME} https://raw.githubusercontent.com/<username>/<project>/<branch>/<path>/<file> &&
source ${FILENAME} &&
rm ${FILENAME}
If you want to ensure the temp file will still go to some predefined directory (such as your home directory) in case of `cd`ing a wrong directory as with `cd /` instead `cd ~`, than you can change the invocation to `tempfile -d ${HOME}`.

Communities

Review Suggested Edit