>>>> "Martin" == Martin Buchholz
<martin(a)xemacs.org> writes:
>>>> "MS" == Michael Sperber
<sperber(a)informatik.uni-tuebingen.de> writes:
>>>> "Martin" == Martin Buchholz
<martin(a)xemacs.org> writes:
>>>>> "SJT" == Stephen J
Turnbull <turnbull(a)sk.tsukuba.ac.jp> writes:
>>>> "mb" == Martin Buchholz
<martin(a)xemacs.org> writes:
SJT> This change can be interpreted as making the treatment of Mule
SJT> consistent between core and packages.
Martin> But it's what the packages do that's broken. Users should think of a
Martin> single set of packages, some of which have attributes, such as
Martin> requiring mule, not two sets of packages.
MS> Well sure, but there we are now: Currently, Mule and no-Mule are
MS> completely different things, and the package system is broken. Once
MS> these two things are fixed (provided they ever will), then we
MS> can---and will---unify these things. I'm only suggesting that we
MS> reflect the current situation accurately, and solve the technical
MS> problem we're having right now.
Martin> I'm not sure I understand what the technical problem is right now. I
Martin> assume we're still trying to solve the excessive stats problem.
Yup.
Martin> What was wrong with my technical suggestion of
Martin> - adding core lisp/ as a hierarchy of depth 0.
Martin> - if mule, adding lisp/mule as another hierarchy of depth 0.
Martin> - adding package hierarchies using a different depth.
Because then, the Lisp code treats the two directories as being
side-by-side whereas the physical relationship is "subdirectory of."
Your stated wish was not to treat mule/ specially, but your suggestion
does just that.
--
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla