[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: xemacs*-mule* add-on package problem



>>>>> On Tue, 17 Jun 2003 06:44:02 +0900 (JST), Tatsuya Kinoshita <tats@vega.ocn.ne.jp> said:

 Tatsuya> The packages mule-ucs, wl, t-gnus, and mhc are grouped into
 Tatsuya> type-B.

 Tatsuya> The packages mew and apel are grouped into type-C.

 Tatsuya> What should be done about type-B and type-C?  (xemacs21
 Tatsuya> and/or emacsen-common be fixed?)

Been thinking about this problem recently and it seems the best
solution would be to do a couple of things:

1) Have the xemacs mule binaries call emacsen-install with the value
   xemacs21-mule and use a dir /usr/share/xemacs21-mule/site-lisp.
2) Have the xemacs non-mule binaries call emacsen-install with the
   value xemacs21-nomule and use a dir
   /usr/share/xemacs21-nomule/site-lisp.
3) Have both packages call emacsen-install with xemacs21 using
   /usr/share/xemacs21/site-lisp.

Then those packages in their respective groups could compile for
whichever set of the three is most appropriate.

Comments?

Jim

-- 
@James LewisMoss <dres@debian.org>      |  Blessed Be!
@    http://people.debian.org/~dres     |  Linux is kewl!
@"Argue for your limitations and sure enough, they're yours." Bach



Reply to: