On 07/28/2011 12:46 PM, Genes MailLists wrote:
On 07/28/2011 06:17 AM, David Sommerseth wrote:
>
> However, I find ~/.local an odd name. To whom or what is it 'local'? If
> you have home directories mounted via NFS and log into two different remote
> hosts via SSH - the only base is "local" to, is the user. But if you
start
> a program which is installed on server but lacks global libraries on the
> other server, then this program is suddenly "local" to a particular server
> in addition. My point is that "local" is very ambiguous and its name is
> poorly chosen. But I realise it's way too late to change "~/.local"
to
> anything now.
>
I just assumed it was by analogy to /usr/local - a per-user directory for local
installation with a structure mimicking /usr.
This is a good point. Especially when you start on a 64 bit box
and
login to a 32 bit (or other arch) - bin now makes now sense at all. You
need arch specific bins (bin, bin64 etc).
Currently Fedora only separates out the /lib* directories in multilib
installations - you'll find a mix of 32 and 64 bit binaries in the system binary
paths on these systems.
Regards,
Bryn.