Le vendredi 25 janvier 2002, à 09:27 PM, David R. Morrison a écrit :
> Are you familiar with the way we are handling perl modules these days?
> There is a "perllocal.pod" file which lists properties of all the
> installed
> modules. We have the package install this as "perllocal.pod.%n"
> (ro
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 so
Are you familiar with the way we are handling perl modules these days?
There is a "perllocal.pod" file which lists properties of all the installed
modules. We have the package install this as "perllocal.pod.%n" (roughly),
and then in a postinstall script, perllocal.pod is created by concatinating
Hi,
In my effort to support Java, I came to 2 conclusions, fink needs to :
1/ source the profile.d script (if there is one) and,
2/ recalculate the CLASSPATH (if JarFiles exists)
in postinstScript. This sounds logical to me and would permit the
in
