Date: Tue, 26 Oct 1999 11:37:01 +0900 From: Shigeyuki Fukushima <shige@FreeBSD.org> To: asami@FreeBSD.org Cc: des@flood.ping.uio.no, shige@FreeBSD.org, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: ports/www/css-mode.el - Imported sources Message-ID: <14357.5069.321000.69482R@athena.sitc.toshiba.co.jp> In-Reply-To: In your message of "25 Oct 1999 14:16:15 -0700" <vqcu2nfp2e8.fsf@silvia.hip.berkeley.edu> References: <199910221609.JAA68294@freefall.freebsd.org> <xzp66zvx24l.fsf@flood.ping.uio.no> <vqcu2nfp2e8.fsf@silvia.hip.berkeley.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
At 25 Oct 1999 14:16:15 -0700,
Satoshi - Ports Wraith - Asami <asami@FreeBSD.org> wrote:
> I've been thinking about an "emacs" category for emacsen and related
> stuff
Very nice too. :)
> but that won't include things like this, which is clearly a web
> utility more than supporting emacs.
I think we need to make this policy clear and documented.
For example, in the above policy, editors/psgml-* ports must be
included in the category of `textproc'.
If `emacs' real category is made, I'll move the following elisp ports (I made)
to this category:
apel-*, bitmap-*, custom-*, flim-*, semi-*, wemi-*.
Firstly, shall we move many emacsen ports?
After this, we need to categorize(= move) emacs-related stuff,
and to modify some of these ports' Makefie which depend on emacsen.
Thanks,
shige
--- shige@FreeBSD.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14357.5069.321000.69482R>