From xemacs-m  Mon Apr  7 18:49:15 1997
Received: from altair.xemacs.org (steve@xemacs.miranova.com [206.190.83.19])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id SAA15761
	for <xemacs-beta@xemacs.org>; Mon, 7 Apr 1997 18:49:14 -0500 (CDT)
Received: (from steve@localhost)
	by altair.xemacs.org (8.8.5/8.8.5) id RAA19240;
	Mon, 7 Apr 1997 17:01:54 -0700
Mail-Copies-To: never
To: xemacs-beta@xemacs.org
Subject: Re: xemacs "flavours" of packages
References: <rvvi5yxw4m.fsf@sdnp5.ucsd.edu>
X-Url: http://www.miranova.com/%7Esteve/
X-Face: #!T9!#9s-3o8)*uHlX{Ug[xW7E7Wr!*L46-OxqMu\xz23v|R9q}lH?cRS{rCNe^'[`^sr5"
 f8*@r4ipO6Jl!:Ccq<xoV[Qz2u8<8-+Vwf2gzJ44lf_/y9OaQ`@#Q65{U4/TC)i2`~/M&QI$X>p:9I
 OSS'2{-)-4wBnVeg0S\O4Al@)uC[pD|+
X-Attribution: sb
From: Steven L Baur <steve@miranova.com>
In-Reply-To: David Moore's message of 07 Apr 1997 16:15:37 -0700
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
Date: 07 Apr 1997 17:01:53 -0700
Message-ID: <m2d8s6s7pq.fsf@altair.xemacs.org>
Lines: 42
X-Mailer: Gnus v5.4.42/XEmacs 20.1(beta12)

David Moore <dmoore@ucsd.edu> writes:

> What is our policy with making XEmacs specific changes to packages?

The changes need to be marked with an `XEmacs' appearing in a comment
nearby.  It is highly useful to take into account what a unified
diff. of the file looks like.  The change hunks should appear marked
(this isn't always possible, but it's nice to try), and gratuitous
formatting changes must be avoided.  The easier a diff is to read,
the easier it will be to maintain until the changes get merged.

> For example, if we added defcustom's to efs (and no efs maintainer was
> on the list) is there a mechanism in place to get that information
> back to the maintainer?

What you should probably do is Cc the maintainer listed at the top
when you submit the patch.  If the file is synched with Emacs (see the 
Synched with: notation at the top) you should make sure the FSF
copyright assignment papers are signed (ftp://ftp.xemacs.org/pub/beta/fsf/)
so the changes can be folded into the official version.  When this is
not done, the changes can disappear off the face of the Earth, like
the unfortunate tale of tpu-edt.el.

> If said maintainer has disappeared off the face of the earth, how
> should we change the version number?  Clearly, we should change the
> version number, but how?

How about appending a -x# to it like Michael has been doing with EFS?

> And is a change in version number being enforced?

No, but it should be.

> Especially things such as supporting custom.el seem like obvious
> changes to get propagated back to maintainers, as that it's
> available in GNU Emacs and XEmacs (at least in the future and
> tiny backward-compat modules exist).

Yup.
-- 
steve@miranova.com baur
Unsolicited commercial e-mail will be billed at $250/message.

