On Thu, Jun 11, 2009 at 7:55 PM, Sergei Golovan <sgolo...@gmail.com> wrote: > severity 532757 wishlist > thanks > > On Thu, Jun 11, 2009 at 3:14 PM, Martin Pitt<martin.p...@ubuntu.com> wrote: >> >> Hello, >> >> The erlang-base package is about 7 MB, which is very large for a >> runtime environment. This is an issue for using e. g. couchdb in an >> embedded environment, or shipping couchdb/erlang runtime on >> distribution CDs (which have limited space). > > 1) I wouldn't like to split erlang-base more (except probably > separating compiler and hipe, but this requires additional > investigations because stdlib has references to compiler and escript > with -mode(compile) directive will not work without compiler too, so > I'd like to be sure that these drawbacks are minor and there aren't > other problems).
I hadn't thought about the interactive shell you get when running "erl" with no arguments. Perhaps that is a reason to not split out the compiler. > 2) As for debug information, it's better to ask upstream first why they > include > debug info and don't give a way to strip it (except patching the > source). I'm afraid that since everyone uses unstripped beam files > then stripping them will reveal some unusual bugs. And I wouldn't like > Debian users to be guinea pigs. As far as running existing applications, I don't think there is much risk: stripped "production" builds are one of the options provided on the CEAN site (http://cean.process-one.net/downloads/) and I've seen it suggested multiple times in the erlang mailing list archives. The existing rules for determining the flags appear to be "build with debug info on all systems except vxworks and ose_ppc750". My guess is that this corresponds to Ericsson wanting debug info on the systems they develop on but smaller binaries on systems they deploy to. I haven't noticed any problems running applications without debug_info if it helps. >> In https://launchpad.net/bugs/385093 we are currently discussing to >> move the debug information out of erlang-base into a separate package >> (this could just go into erlang-dev, or into a new erlang-debug). >> >> We would like to modify the package so that erlang-base gets stripped >> libraries (with e. g. erts/emulator/utils/make_preload beam_strip()) >> and that erlang-debug would ship the unstripped libraries in an >> alternate preferred library search path. >> >> However, we don't want to do this without your consent/acceptance of >> the patch, since that would introduce a large incompatibility of >> reverse dependencies between Debian and Ubuntu. > > 3) Currently, Erlang in Ubuntu is essentially unmaintained, so keeping > compatibility with Debian packages is reasonable. But if you will > maintain it (and fix Ubuntu-specific bugs) then I don't see why > compatibility is necessary. Compatibility makes it easier to pass changes back and forth between the two distributions. I doubt our user bases are that different (some want to develop Erlang apps, some want to run Erlang apps), so it seems worthwhile trying to cooperate. Our main goal here is to get the basic runtime down small enough so that we can get an Erlang based application (CouchDB) onto the Ubuntu install CD. I imagine that these improvements could also be useful for Debian users wanting to deploy systems with limited storage space. James. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
