You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The download instructions might just inform the user to "obtain software from vendor" type message, but might not tell the user exactly what filenames are expected, and where to put them. Rather than relying on each download instruction to keep the version string and whatnot up-to-date in the instructions, better to just have this output clearly written out in the stdout message.
== fetching files...
Download instructions:
Blablabla current instructions foobar sources from https://download.foobar.com manually
---
Put "foobar-1.2.3.tar.gz" in
/apps/sources/f/foobar/
or something along those lines. Maybe even print the checksum along with it?
You must provide the following sources:
"/apps/sources/f/foobar/foobar-1.2.3.tar.gz" sha256sum: 3a71565a4fb114a2f9af9a1710bd3160781a7566bb2746bef1ba8af372b4d7b0
I know the source directory can be multiple locations, but it could at least suggest the sourcepath/f/Foobar/ type path where I think most people end up storing them and where the download would occur if it could be downloaded.
The text was updated successfully, but these errors were encountered:
The download instructions might just inform the user to "obtain software from vendor" type message, but might not tell the user exactly what filenames are expected, and where to put them. Rather than relying on each download instruction to keep the version string and whatnot up-to-date in the instructions, better to just have this output clearly written out in the stdout message.
or something along those lines. Maybe even print the checksum along with it?
I know the source directory can be multiple locations, but it could at least suggest the
sourcepath/f/Foobar/
type path where I think most people end up storing them and where the download would occur if it could be downloaded.The text was updated successfully, but these errors were encountered: