Roland Mainz writes: > > So what can the justification be? > > There is no justification right now.
OK. > And based on the current discussion > there will never be the need to move the libraries from /usr/lib to /lib > because we won't start or porpose any projects if libshell ends in > /usr/lib from the beginning. Huh? > Just one example: A while ago two of our > students were working on adding SCTP support (while I was doing > experiments with adding SCTP support to ksh93) to SMF which required > linkage against libsctp. At this point the students were faced with an > ARC case to get libsctp moved to /lib (at this point the > ksh93-integration ARC case wasn't running and noone else here had any > experience with it) and simply backed-off and requested a different > project because the inability to predict a possible outcome was not > suited for a students project. Sorry, I don't follow. Just because someone apparently didn't have the intestinal fortitude necessary to complete the project doesn't mean that the project cannot be done and is certainly not evidence that the ARC is causing a problem here. In the specific example you're talking about, the move is _trivial_. The existing libsctp.so.1 on Solaris depends only on things in /lib. The only reason it's not in /lib is that there's nothing in the root file system that needs it. The first project that needs it there can move it. It's a no-brainer. > And the same issue applies to any work on the events framework for SMF, > too. If someone would start such a project which requires to move the > libraries sooner or later the people will read this discussion (and > ARC's rejection of keeping the libraries in /lib) and I think the > immediate reaction will simply be that they request another assignment - > just anything else which doesn't deal with moving libshell around again. I'm sorry to hear that there are people who scare so easily. They're likely to have a lot of trouble with software. If someone in that hypothetical future project actually reads this case, he will, with any luck at all, see that we've stated *MULTIPLE* times that moving the libraries from /usr/lib to /lib is trivial. It's easy to do. It involves minimal and straightforward work. None of us are opposed to it, provided there's a reason. The one thing it does require is justification. There must be a reason to do it. Once you have that, the rest is a non-issue. If you're somehow reading this as a "rejection" of placing the libraries in /lib, then I think you've misunderstood. That's not what it is -- it's just that no ARC member reviewing the case has seen a clear need to have any of this in the root file system. There may be a future in which we need the libraries in the root file system. If that future comes to pass, we'll revisit the question. -- James Carlson, KISS Network <james.d.carlson at sun.com> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
