From owner-freebsd-ports@FreeBSD.ORG Sun Jun 29 09:44:48 2003 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F09F37B404 for ; Sun, 29 Jun 2003 09:44:48 -0700 (PDT) Received: from alcoholic.geiin.org (fc040109.os.FreeBit.NE.JP [43.244.40.109]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4227143FE5 for ; Sun, 29 Jun 2003 09:44:47 -0700 (PDT) (envelope-from yoichi@geiin.org) Received: from fc040109.os.FreeBit.NE.JP (vaio.local-net [10.0.0.3]) by alcoholic.geiin.org (Postfix) with ESMTP id 74DD21EB20 for ; Mon, 30 Jun 2003 01:44:46 +0900 (JST) Date: Mon, 30 Jun 2003 01:46:24 +0900 Message-ID: <871xxcu90f.wl%yoichi@geiin.org> From: Yoichi NAKAYAMA To: freebsd-ports@freebsd.org User-Agent: Wanderlust/2.11.3 (Wonderwall) KARAMI/1.14.2 (TABASCO) FLIM/1.14.5 (=?ISO-2022-JP?B?GyRCPVBELkx4GyhC?=) APEL/10.5 Emacs/21.2 (i386-debian-linux-gnu) MULE/5.0 (=?ISO-2022-JP?B?GyRCOC1MWhsoQg==?=) Organization: Geiin.org X-Face: wLZki+KbGjgKe0,<&3g*rA|R**vj[a8L%[v]ecJh1L(Uqm|LBx; v7Nq7n%?0d.aS]F#[~C\!{m?m,C&#U5}$_pZvBR>5VmX1Ol0`P\M-U8`sUF<5Quj'z&zzW8r|Zl9#W7Wut3duYzpKrP{n+AbarKtJ!i"Al7]P;-?[=iBZa*]r=>C':0~JECx]IH+RXq=/hUX}MB9e]oQKBxsDd/ X-Weather: =?ISO-2022-JP?B?GyRCOiNGfCROQmc6ZUlcJE9AMjhlRl4kRyQ5GyhC?= X-SKK: Daredevil SKK/12.1.1 (Okamachi) MIME-Version: 1.0 (generated by KARAMI 1.14.2 - "TABASCO") Content-Type: text/plain; charset=US-ASCII Subject: proposal: improve emacs lisp ports handling X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2003 16:44:48 -0000 Hi, I'd like to propose a way to improve elisp ports handling in FreeBSD ports system. Abstract: I will propose a way to handle elisp modules. An elisp ports will be able to provide byte-compiled elisp files for several emacsen without conflict. Problems: 1) byte-compiled elisp files depend on the version of emacsen. So we should * byte-compile by some specific emacsen. (one solution for this is to split the port into several ports and use bsd.emacs.mk respectively.) or * install without byte-compilation ** one example of the former is [1], where elisp directory is not version specific so we cannot install them simultaneously. ** another example of the former is [2], where elisp directory is version specific. The package generated by this may become different if bsd.emacs.mk is changed (e.g. release of newer version of emacsen) even if the version of the port itself is not changed. (related issue is described in [3]) ** example for latter case is [4] but this cannot be accepted for larger modules, where byte-compilation will shorten their loading time. 2) conflict of binaries and documents (include info) [5] * one solution is to split port so that one is for elisp installation and the other for installation of binaries. [6] * splitting document part for every elisp ports is a stupid way. I think we should find the solution to these problems "without having many bunches of duplicate ports". An idea: 1) a elisp port will install sources (*.el) with documents and binaries. 2) byte-compilation will be triggered by installation/deinstallation of emacsen ports and elisp ports A tentative implementation of this idea can be found in http://cvs.arege.net/ports-elisp/ Comments and/or suggestions are welcome. Reference: [1] ports/editors/psgml and ports/editors/psgml-* [2] ports/mail/wanderlust and ports/mail/wanderlust-* [3] ports/50799: Lisp Packages install directory should not depend on minor emacs version [4] ports/audio/mpg123.el [5] ports/mail/mew2 and ports/mail/mew2-* [6] ports/irc/liece-dcc and ports/irc/liece, or ports/japanese/migemo and ports/japanese/migemo-* [7] The idea is inspired by emacsen-common package in Debian Best regards, -- Yoichi Nakayama FreeBSD ports committer / yoichi@FreeBSD.org