Michael Sperber writes:
Robert Widhopf-Fenk <hack(a)robf.de> writes:
> But taking a look at the package of gnus I started to modify
> it to match the layout of upstream which simplifies syncing
> a lot.
>
> Are such changes o.k.?
Yes. (By me at least.) The easier it is for you, the better---just as
long as the package infrastructure works correctly for your code, and
that seems to be the case.
+1
N.B. The only developers that really matter in this respect are
Norbert and Robert. Package maintainers should also pay careful
attention to comments by Steve Youngs and Ville Skyttä -- as former
avatars of the package czar, their advice is sure to be useful.
Robert, I assume that you want to keep the VM version number in sync
with its XEmacs package version, as Kyle did. However, XEmacs package
versions are not compatible with double-dot versions, AFAIK. Please
consult with Norbert and maybe Steve Y and Ville about that.
> The list of provides in "package-info.in" has to be
updated
> by hand if I am correct?
I think so.
Again AFAIK, at present, yes. Automating it should be easy and is a
good idea. Feel free to file a feature request on the tracker so we
don't forget it.
> Also I bundle a newer version of vcard.el with vm, than the
> one provided by the gnus package. How are such duplicates
> handled? IMHO it would be better to have vcard.el in another
> package required by the packages which need it.
We already do this kind of thing for several libraries. mail-lib is
probably a good place.
You should consult with Norbert (who will be in charge of making sure
that vcard.el ends up somewhere reasonable) and Mike Kupfer
(maintainer of XEmacs's Gnus package) about this.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta