|--==> "SJT" == Stephen J Turnbull <stephen(a)xemacs.org> writes:
SJT> Steve: is there some way that people with commit privileges can be
SJT> allowed to create packages in CVS without interfering with your work?
SJT> I'm thinking about something like adding a
SJT> .../alpha-packages/$developer-name/$package-name hierarchy parallel to
SJT> the "official" .../packages/xemacs-packages hierarchy.
Sure. I'll create directory under XEmacs/packages/ called
"unsupported". With a README containing the appropriate warnings and
disclaimers.
I'd rather call it "unsupported" than "alpha-packages" to reduce
confusion.
SJT> I'm just guessing, but probably we can just drop the standard
SJT> makefiles and XEmacs.rules (maybe with STAGING defaulting to somewhere
SJT> other than the usual "official packages" STAGING) in there.
More than likely. My only requirements are what I mentioned in
another post to this thread. Namely:
- They install to /site-packages/
- They don't have a _pkg.el file.
- They don't have a package-index file.
Those last two points will change, but PUI needs enhancing first.
--
|---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|