Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 21 May 1999 13:44:05 +0200
From:      Michael Elbel <Michael.Elbel@consol.de>
To:        asami@FreeBSD.ORG
Cc:        ports@FreeBSD.ORG
Subject:   Re: Do you need editors/xemacs{,20} (Re: pending/11618: new port: editors/xemacs21)
Message-ID:  <19990521134405.A793@consol.de>

next in thread | raw e-mail | index | archive | help
In lists.freebsd.ports you write:

> * From: Jacques Vidrine <n@nectar.cc>

>Ok, Taoka-san, please yell when you're ready, and I'll do the copy
>from xemacs20, which is much closer to xemacs21 than xemacs(19).

>xemacs has a much richer history, but unfortunately it wasn't
>repository copied when xemacs20 was brought in -- so that part will be
>lost forever when it's removed.

Hrm. I sent a reply to this thread yesterday, but it seems to have gone
down the bitbucket somewhere :-(

As the current maintainer of the xemacs and xemacs20 ports, I'm not quite
sure how to go on about xemacs-21 since there's a couple of issues that
probably should be resolved:

 - I think it would be feasible to keep the xemacs20 port around,
   they have changed the way elisp packages are distributed and I can
   imagine quite a few people that might want to stay with 20.4 no
   matter what. Yes, they are at xemacs-21.1.2 now and it is very stable,
   but nevertheless ...

 - I think it would be wise to *have* the major number in the port name
   (similar to what e.g. mysql and netscape has) simply so people know
   what's going on - but I'm perfectly willing to be overruled by
   people more knowledgeable than me, especially our esteemed ports
   meister.

 - In this vein, would it make sense to make a repository copy from
   xemacs20 to xemacs21 and *keep* 20? That'd give us a complete history
   even if/when the xemacs20 port gets deleted in the future.

 - We currently have a mule option in the "base port". Now we also have
   the explicit mule ports as well. Are there actually people who use
   the mule stuff with editors/xemacs20? I get the feeling that it might
   be better to drop mule support in the "base" port and let people who
   know more about that stuff handle it in the explicit ports.

 - As I mentioned further up, with xemacs-21, the handling of elisp
   packages has changed. Earlier releases came with a full set of
   lisp packages. Now almost everything is distributed as separate
   "packages". This means that a port without any packages, as submitted
   in pending/11618, is nearly useless. I see two solutions to that:

   - Distribute a reasonable set of packages with the actual xemacs port.
     this requres some Makefile hackery since the packages reside in
     different dirs on the servers as the rest of xemacs.
   - provide a reasonable (or not so reasonable :-) set of packages
     as a seperate port (editors/xemacs-packages).

   I'm currently leaning toward the later solution since it decouples
   packages from the base, which reflects what the xemacs people themselves
   wanted in the first place. Right now I have the following packages
   installed in my /usr/local/lib/xemacs/xemacs-packages:

       size  name
       69913 c-support-1.12-pkg.tar.gz
      186436 cc-mode-1.13-pkg.tar.gz
      103161 debug-1.09-pkg.tar.gz
      187654 dired-1.05-pkg.tar.gz
      577970 edit-utils-1.39-pkg.tar.gz
      369742 efs-1.14-pkg.tar.gz
       17347 fsf-compat-1.05-pkg.tar.gz
     1873480 gnus-1.40-pkg.tar.gz
      131968 mail-lib-1.23-pkg.tar.gz
      107193 net-utils-1.11-pkg.tar.gz
      228261 os-utils-1.15-pkg.tar.gz
      596965 prog-modes-1.19-pkg.tar.gz
      425458 psgml-1.12-pkg.tar.gz
       26938 sgml-1.04-pkg.tar.gz
      207865 text-modes-1.19-pkg.tar.gz
       20006 time-1.07-pkg.tar.gz
      317899 viper-1.14-pkg.tar.gz
      430640 xemacs-base-1.30-pkg.tar.gz
       83543 xemacs-devel-1.21-pkg.tar.gz

   one could probably leave gnus with its almost 2MB off if not too many
   people scream, after all there's a nice pagage-retrieval mechanism
   right there in xemacs.

Ok, enough blubbering, I'm in the middle of implementing the mule-less port
with separate packages port. If nobody shouts, I'll finish it over the
weekend. If there is somebody else who wants to reliably take over the
maintenance of the base xemacs ports, please speak up and I'll retire (it's
not as if I don't have enough other things to do).

Michael

-- 
\|/
-O- Michael Elbel, ConSol* GmbH, - me@consol.de - 089 / 45841-256
/|\ Fermentation fault (coors dumped)


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message




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