Date: Tue, 23 May 2006 22:03:38 +0200 From: Mark Evenson <evenson@panix.com> To: pav@FreeBSD.org Cc: freebsd-ports@FreeBSD.org Subject: Re: setting EMACS_PORT_NAME=emacs22 forks make infinitely at the port registration step Message-ID: <44736A9A.6050201@panix.com> In-Reply-To: <1148412647.61285.21.camel@ikaros.oook.cz> References: <200204301328.g3UDS9X43078@thelonious.eziba.com> <e4vm6k$obv$1@sea.gmane.org> <1148412647.61285.21.camel@ikaros.oook.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
Pav Lucistnik wrote: > Mark Evenson píše v út 23. 05. 2006 v 21:01 +0200: > >> Am I using the EMACS_PORT_NAME variable correctly? (i.e. its not a >> forbidden user knob like USE_XXX) > > You must never set up any internal variables. This is one of them. > You should limit yourself to WITH_*, WITHOUT_*, and the variables > explicitly documented in end user documentation. > Dumb question: what do you mean by end user documentation? What the port emits to the console in the process of building plus available options stored under /var/db/ports? Andrey Slusar's reply to this thread [[1]] seems to imply that EMACS_PORT_NAME *is* a end user option. But then you have a @freebsd.org address and he doesn't… Without an end-user mechanism like EMACS_PORT_NAME, maintaining all Emacs dependent ports for separate versions of Emacs will get combinationally explosive. So ports just supports one canonical version of Emacs (what's in editors/emacs) for all Emacs add-ons (like psvn, nxml, etc.)? Thanks for the clarification. --- [[1]] news://news.gmane.org:119/86bqtoy1m1.fsf@santinel.home.ua
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44736A9A.6050201>