On Wed, Dec 09, 2009 at 07:56:39AM -0500, [email protected] wrote: > But how much do those ports actually depend on that specific emacs build? > Shouldn't other ports be able to use either emacs or emacs-app-devel? The > emacs-app-devel port will load lisp files from ${prefix}.
I think in most (all?) cases the dependency is only that the portfiles happen to list dependencies on port:emacs rather than some sort of actual dependency. Should we have a metaport to act as a dependency for "any version of emacs"? Currently there's at least emacs, emacs-app, and emacs-app-devel; I could also see a need for an emacs-devel or perhaps separate ports for 22 and 23. It would also be nice if eventually we could have installed lisp packages byte-compiled for all installed emacs versions, like Debian's emacsen does, but that sounds like a much more involved project. Dan -- Dan R. K. Ports <[email protected]> Research Henchman Massachusetts Institute of Technology <[email protected]> Computer Science and Artificial Intelligence Lab <[email protected]> _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
