David R. Morrison [[EMAIL PROTECTED]] wrote: > Maybe something like this could work for CLASSPATH? Each package providing > its ingredients, stored in a good place, and then some file specifying > the full CLASSPATH is created in postinstall out of all of these? (Which > the user would get by sourcing profile.d ...)
This makes sense... maybe each package would make a file with a list of classpath dependencies: %p/lib/package/package.jar %p/etc/package-conf ...and then those files could be used for generating CLASSPATH at login time, and the build scripts could also regenerate it just before building any new package so that CLASSPATH would always be up-to-date when building new java packages. > Just a rough idea, needs some work, but I think it is feasible. I agree, that would solve it... -- Ben Reed a.k.a. Ranger Rick ([EMAIL PROTECTED]) http://defiance.dyndns.org/ / http://radio.scenespot.org/ Frankenstein was the creator -- not the monster. It's a common misconception, held by all truly stupid people. -- Kryten _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
