DJ Lucas wrote: > Actually I still need feedback from somebody who actually uses it. I > fixed the logic, at least in testing in a regular /etc/profile, but I've > not tested in the actual profile.d script. I don't use the directory > based profile setup nor the auto classpath myself. > > To test, put a single jar file whose name contains a space into the > CLASSPATH directory, then re-source the profile and see if duplicate > entry exists or a ':' (colon) character exists where a space should be. > It should work, and did locally. I had actually thought about > suggesting that we rip it out completely and just set > CLASSPATH="$CLASSPATH:." by default.
DJ, you are the most knowledgeable editor in this area. Do whatever you think best. Every package does not have to conform to the profile.d mechanism. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
