Date: Mon, 22 Aug 2011 16:25:40 GMT From: Till Klampaeckel <till@php.net> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/160003: drop lang/erlang-lite and update lang/erlang Message-ID: <201108221625.p7MGPeVp034219@red.freebsd.org> Resent-Message-ID: <201108221630.p7MGUINM003662@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 160003 >Category: ports >Synopsis: drop lang/erlang-lite and update lang/erlang >Confidential: no >Severity: critical >Priority: medium >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Mon Aug 22 16:30:18 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Till Klampaeckel >Release: latest >Organization: >Environment: >Description: The two ports create issues for the several ports relying on them: * databases/couchdb * net-im/ejabberd Most/All these (server) ports don't require Erlang with a full-fledge Java, X11 and/or ODBC install but when they rely on lang/erlang-lite instead, it creates unnecessary conflicts when someone has lang/erlang installed already. The other option is to adjust the Makefiles of those ports -- which makes them unnecessary complicated also. My proposal is to drop lang/erlang-lite and change lang/erlang to behave like lang/erlang-lite currently does by default. In addition, lang/erlang would then accept WITH_JAVA, WITH_X11, WITH_ODBC and WITH_SMP so users can still get the "full" environment installed. Though I think the majority of Erlang users or the ports relying on this port won't need this often. I can help updating the port or at least test updates. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201108221625.p7MGPeVp034219>