Josh Hurst wrote: > > Do you not have arguments to put the libraries into /lib and you do > not have any arguments against it. > Roland and April are laying the foundation for future work and in my > opinion it should be their decision where they want to place the > libraries.
WRONG! - He says in his best game show voice. :) If we let individual project teams or developers place binaries and libraries where they think best then it would be chaos. Maintaining consistent policies around file system location is a good thing. In the past we've struggled with that inside of Sun and though we sometimes refuse to learn from our mistakes we certainly remember them. Your argument above basically breaks down to "everything that isn't prohibited should be allowed" and thats a recipe for disaster. As multiple people have clearly pointed out multiple times there needs to be a reason and purpose for the changes one makes. If there is no reason other then, "Well maybe in the future we might have to do X" then it's not good enough. When it is time to make future changes a project team can ask for dependent changes to be made at the same time. If that means putting ksh into /sbin, or changing roots shell, or what have you....we'll discuss those changes at that time and not before. Everyone wants a new version of ksh on the system. (Hell I still use csh and now even I'm cheering for it ... ) We all want it done correctly is the take-a-way.
