On 07/28/2011 09:09 AM, Bryn M. Reeves wrote: > On 07/28/2011 01:41 PM, Genes MailLists wrote: >> On 07/28/2011 07:53 AM, Bryn M. Reeves wrote: >>> On 07/28/2011 12:46 PM, Genes MailLists wrote: >> >>>> 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. >>> >> >> which is fine for a 'system' which is 64 bit and may support 32 bit as >> well - its not fine for a 'user' who logs in to a 32 bit machine from a >> 64 bit machine and now his binaries wont work. > > Separating bin paths like this would not solve the problem; anything that's only > present in one path or the other would still fail in the scenario you suggest. > You could equally install foo/foo64 or vice versa into the same directory. > I don't follow your thought here - if you have a bin64/ and a bin/ etc and you have your shell initscripts decide (e.g. using uname -m) which of those to include in your PATH I think it does work ... provided you have (obviously) both (all) populated with whats needed... gene -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
