[erlang-bugs] Be able to handle more than one repasitory of software
Fri Nov 17 13:47:26 CET 2006
In my system, Erlang is installed in /usr/lib/erlang so I have a repository of
software, I mean, libraries at /usr/lib/erlang/lib. With lots of nice
libraries. All those files are managed by a package manager that does a good
job of upgrading my installation whenever a new package is released.
Now, I do some coding and I don't want my code in there as well for various
reasons among them that it is not managed by the package management, it is
experimental and it install more files that should also don't go directly
I normally install on /usr/local so my libraries go
into /usr/local/lib/erlang/lib. I don't see any way to tell erlc to also look
for libraries in /usr/local/lib/erlang/lib and this is my bug report. I
believe there should be a way. There's -pa, but that requires specifing each
library path and not a repository of libraries.
Just to make my case a little bit clear, this is how it is done with other
- C: there are so many ways to do it here. With gcc you can use
LD_LIBRARY_PATH to list all the places were you can find libraries. You can
also set it in ld.so.conf or you can add it to the command line with -L
(and -I for the includes).
- C++: Same as C.
- Obj-C: Same as C.
- Python: You just set PYTHON_PATH to contain the extra directories to search
- Haskell: Using ghc you can use the parameter -i to add paths to search for
modules. I don't know if there's an environment variable to do it, but I am
sure there is.
- Ruby: You can do it, if I understand it correctly, with -I.
- Java: long ago I remember setting a CLASSPATH environment variable, but I am
not completely sure.
I believe it is important to give good support for this kind of features that
are just expected to be there by people using OSs just as GNU/Linux and tools
such as make, automake/conf, etc.
Pupeno <> (http://pupeno.com)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 198 bytes
Desc: not available
More information about the erlang-bugs