Directory for executable files

[Robert Heller]

At Tue, 21 May 2019 10:05:03 +1000 "Ubuntu user technical support,  not for general discussions" <ubuntu-users at lists.ubuntu.com> wrote:

> 
> Thank you for reading this.
> 
> In the past, programmes that needed to be built were downloaded into 
> /usr/local/src and once "configure" and "make" were run an executable 
> file would end up in /usr/local/bin. I don't often need to build a file 
> with "make" and instead many of the programmes that I've downloaded, 
> often to take advantage of the latest version, are downloaded in a zip 
> file that contains an executable file.
> 
> Once extracted the executable file, along with many other files, ends up 
> in ~/Downloads/programme_name but of course that directory is not in 
> $Path. "Application Launcher" takes care of that problem but I think 
> there must be a more technically correct method.
> 
> I do have ~/.local/bin because that's where "pip" puts the executable 
> files. I could link ~/Downloads/programme_name to ~/.local/bin and that 
> would allow me to launch an executable file from the console. $PATH 
> includes ~/.local/bin.
> 
> So, is using the application launch the best method to take care of 
> programmes that are not in the path or is there a more technically 
> correct and neater method?

*Some* of us 'Old Timers' have a directory $HOME/bin on our $PATH and have 
various programs there (often one-of programs and scripts, many lacking any 
sort of makefile or anything like that).

> 

-- 
Robert Heller             -- 978-544-6933
Deepwoods Software        -- Custom Software Services
http://www.deepsoft.com/  -- Linux Administration Services
heller at deepsoft.com       -- Webhosting Services