| 1 |
Hi, |
| 2 |
|
| 3 |
At Sun, 16 Nov 2003 17:33:14 -0600, |
| 4 |
Matthew Kennedy wrote: |
| 5 |
|
| 6 |
> * Firstly, please review this: |
| 7 |
> |
| 8 |
> http://dev.gentoo.org/~mkennedy/emacs/site-gentoo.el-rfc.txt |
| 9 |
|
| 10 |
I'll second it. It will also solve http://bugs.gentoo.org/show_bug.cgi?id=10742 |
| 11 |
|
| 12 |
> * Install elisp source in such a way that global recompilation is |
| 13 |
> possible. |
| 14 |
|
| 15 |
> I suggest we provide a way to recompile all .el files for elisp add-on |
| 16 |
> packages (typically from the app-emacs/ category, but also from |
| 17 |
> ebuilds supporting the emacs USE flag). This mechanism should be |
| 18 |
> called whenever a new emacs upgrade is performed. |
| 19 |
|
| 20 |
I think the feature what you suggest here is not emacs specific but |
| 21 |
global. For example, when people bumped openssl version 0.9.6 to 0.9.7 |
| 22 |
we saw many breakages and needed to run revdep-rebuild by hand. |
| 23 |
However, if we had a variable in ebuild that tells Portage "all |
| 24 |
the ebuilds that depend on me should be compiled again after emerge" |
| 25 |
we wouldn't come across the problem. If this feature is implemented |
| 26 |
into Portage we will have no problem not only with ebuilds in |
| 27 |
app-emacs but also with other ebuilds supporting emacs USE flag |
| 28 |
(because such ebuilds depend on virtual/emacs). |
| 29 |
|
| 30 |
> * Your Thoughts Here... |
| 31 |
|
| 32 |
I wonder why we don't have xemacs herd. Some of the bugs in bugzilla |
| 33 |
were assigned to emacs@g.o after the alias was created, but I think |
| 34 |
xemacs herd should be created and these bugs will be assigned to that |
| 35 |
herd. There are two reasons for it. First, as I see from ChangeLogs in |
| 36 |
app-xemacs category, xemacs packages are maintained by agriffis, |
| 37 |
rendhalver and rac (they don't commit to app-emacs and those who |
| 38 |
commit to app-emacs don't touch app-xemacs). Second, FSF Emacs and |
| 39 |
XEmacs have different packaging policy and should be considered |
| 40 |
separetely (I'm not using XEmacs, so I should ask XEmacs people before |
| 41 |
I do any changes if it is assigned to emacs herd). We could have |
| 42 |
meta-emacs herd to which both emacs and xemacs herd belong, but that |
| 43 |
will be a different issue we might consider after creating xemacs |
| 44 |
herd. |
| 45 |
|
| 46 |
Any comments? |
| 47 |
|
| 48 |
-- |
| 49 |
Mamoru KOMACHI <usata@g.o> |
| 50 |
http://www.gentoo.org/~usata/ |
| 51 |
|
| 52 |
-- |
| 53 |
gentoo-dev@g.o mailing list |
Archives