Re: ess package status?
Stephen J. Turnbull wrote:
A.J. Rossini writes:
> It's an issue with maintainer stress, dealing with getting upstream
> into XEmacs package repo with minimal problems.
>
> Simple, easy build tools and patches for such welcome (send such to
> ESS-help list or ESS-bugs list)
Can you be more specific about the problems these tools are supposed
to solve?
My understanding from what Rodney said at the time was that simply the
effort of copying the code into a checkout of ESS from XEmacs CVS and
doing a test build was costing too much time and effort given the
activity of the ESS project, and his goals for the timeliness of
XEmacs package releases of ESS. Frustration with timeliness (rather,
the lack of it) was further aggravated by the lags imposed by the
package and SUMO release cycles.
Beyond my other issues, I don't think I have previously expressed the
following point... What is also cumbersome and annoying is the need to
create a separate package for everything: xemacs, Debian, Fedora, Fink,
FreeBSD Ports, etc. Where does it all end? And, to top it off, all of
this is completely unnecessary. All that it is required is for the
users to read the installation instructions which can be found in the
distro or online ＠
http://ess.r-project.org/Manual/ess.html#Installation
Rodney
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta