From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27016 invoked by uid 1002); 17 Nov 2003 15:40:09 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 5854 invoked from network); 17 Nov 2003 15:40:09 -0000 Date: Tue, 18 Nov 2003 00:40:02 +0900 Message-ID: <86ptfrgg19.wl%usata@gentoo.org> From: Mamoru KOMACHI To: gentoo-dev@gentoo.org In-Reply-To: <87r807c2it.fsf@killr.ath.cx> References: <87r807c2it.fsf@killr.ath.cx> User-Agent: Wanderlust/2.11.20 (Wonderwall) SEMI/1.14.5 (Awara-Onsen) LIMIT/1.14.7 (Fujiidera) APEL/10.6 Emacs/21.3 (i686-gentoo-linux-gnu) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII Subject: [gentoo-dev] Re: (emacs) proposed site-lisp and byte-compilation improvements X-Archives-Salt: df9ab9d7-d8cd-4c09-a063-3c430a5a7526 X-Archives-Hash: 624f952a94bf46a8046cddf851f46c06 Hi, At Sun, 16 Nov 2003 17:33:14 -0600, Matthew Kennedy wrote: > * Firstly, please review this: > > http://dev.gentoo.org/~mkennedy/emacs/site-gentoo.el-rfc.txt I'll second it. It will also solve http://bugs.gentoo.org/show_bug.cgi?id=10742 > * Install elisp source in such a way that global recompilation is > possible. > I suggest we provide a way to recompile all .el files for elisp add-on > packages (typically from the app-emacs/ category, but also from > ebuilds supporting the emacs USE flag). This mechanism should be > called whenever a new emacs upgrade is performed. I think the feature what you suggest here is not emacs specific but global. For example, when people bumped openssl version 0.9.6 to 0.9.7 we saw many breakages and needed to run revdep-rebuild by hand. However, if we had a variable in ebuild that tells Portage "all the ebuilds that depend on me should be compiled again after emerge" we wouldn't come across the problem. If this feature is implemented into Portage we will have no problem not only with ebuilds in app-emacs but also with other ebuilds supporting emacs USE flag (because such ebuilds depend on virtual/emacs). > * Your Thoughts Here... I wonder why we don't have xemacs herd. Some of the bugs in bugzilla were assigned to emacs@g.o after the alias was created, but I think xemacs herd should be created and these bugs will be assigned to that herd. There are two reasons for it. First, as I see from ChangeLogs in app-xemacs category, xemacs packages are maintained by agriffis, rendhalver and rac (they don't commit to app-emacs and those who commit to app-emacs don't touch app-xemacs). Second, FSF Emacs and XEmacs have different packaging policy and should be considered separetely (I'm not using XEmacs, so I should ask XEmacs people before I do any changes if it is assigned to emacs herd). We could have meta-emacs herd to which both emacs and xemacs herd belong, but that will be a different issue we might consider after creating xemacs herd. Any comments? -- Mamoru KOMACHI http://www.gentoo.org/~usata/ -- gentoo-dev@gentoo.org mailing list