For Java-based packages, Fink keeps track of the current CLASSPATH setting in the /sw/share/java/classpath file. Packages also store their JAR files in /sw/share/java/%n. This causes a name collision if a package happens to be named "classpath": Fink will put the package's JARs into a directory called /sw/share/java/classpath, but it will also try to create a file called /sw/share/java/classpath. Kaboom!
Of course, this problem only occurs with one package -- the one for the GNU Classpath project -- and could be worked around by renaming it to gclasspath, for example. Still, packages should not have to be renamed just because Fink puts a file in the wrong place. Fink should instead use a different file name, such as classpath.txt, to store the CLASSPATH. Thoughts? Trevor ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Fink-devel mailing list [email protected] http://news.gmane.org/gmane.os.apple.fink.devel
