Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 23 Mar 2004 22:33:33 -0800
From:      Kris Kennaway <kris@obsecurity.org>
To:        Kaarthik Sivakumar <kaarthik@comcast.net>
Cc:        freebsd-ports@freebsd.org
Subject:   Re: xemacs-devel port
Message-ID:  <20040324063333.GA44331@xor.obsecurity.org>
In-Reply-To: <86oeqmq0hg.fsf@comcast.net>
References:  <200403231920.i2NJK4Bx004045@peedub.jennejohn.org> <86oeqmq0hg.fsf@comcast.net>

next in thread | previous in thread | raw e-mail | index | archive | help

--FCuugMFkClbJLl1L
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Mar 24, 2004 at 12:26:35AM -0500, Kaarthik Sivakumar wrote:
> >>> "GJ" =3D=3D Gary Jennejohn <garyj@jennejohn.org> writes:
> GJ> Wouldn't hurt since I, the maintainer, can't get into freefall to
> GJ> do any commits.
>=20
> Ok, I will file a pr.
>=20
> GJ> This is really a nit! xemacs has bigger problems, but what the
> GJ> heck.
>=20
> I know, but a user did mention on the xemacs-beta mailing list that
> 21.5 is gamma and that raised concerns there about our packaging. So..
>=20
> What bigger problems do you see with xemacs? I run
> compiled-from-source xemacs 21.5.x and other than standard beta
> software problems with xemacs in general (ie not FreeBSD specific),
> everything seems ok. I use compiled-from-source 21.4 at work and that
> is quite good.

Any chance you could submit a patch to update the ports to the current
versions?  They're a bit behind right now.

Kris

--FCuugMFkClbJLl1L
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQFAYSu9Wry0BWjoQKURAivhAJ42P1LenoaD75zqjMpdL8vcqtiJgwCgvwFn
NvqpLdWo0jXxFFqepDm+qOg=
=MB/4
-----END PGP SIGNATURE-----

--FCuugMFkClbJLl1L--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040324063333.GA44331>