> > I'm a total plan9 newbie, but I hate polluting / with every single > > application. I do prefer to have all apps in a single package directory > > /$some_dir/$objtype/bin where $some_dir is /opt, /pkg, /contrib, etc. I do > > not know if this would fit in well with the plan9 way though... > > > You wouldn't be `polluting' / with every single application. Binaries would > either go in $user/bin and would be then be bind-ed to /bin, or binaries would > just go in /$objtype/bin. No `pollution' here.
Following on what Ron said earlier, I prefer to leave / untouched. If programs are installed into /$app_name/..., you end up with variants of /acme/*, /rc/*, /tex/*, /troff/*, /tex/*, /my_fav_pub_app/... That is what I meant by pollution. Do you consider this desirable? Maybe we are talking apples and oranges here. I'm also talking about system wide apps on a multiuser system. So, for example, your /$objtype/bin would look something like /sys_apps/$objtype/bin, and /sys_aps would contain all system wide, non-OS distributed, applications. Hope I have not offended here. EBo --
