Re: How to make a package for XEmaacs
On 10/17/2011 6:32 AM, Stephen J. Turnbull wrote:
smitchel writes:
> I can find descriptions of the package system, how to use it to update
> your packages etc, but I am not finding a step by step list of
> directions to make some lisp code and some documentation into a package.
> Is there such a list, and if not, where do I go to learn how to make a
> package?
> From your description, I don't think you're referring to the node in
the Lispref. Eval the following form and tell me if that helps:
(Info-goto-node "(lispref)Packaging")
Thank you. That does help. I
still have some doubt about parts of it.
I will work on this information and try to get it in a list and see
where I still am in the dark, then ask more specific questions.
Note that if you're going to contribute the package to XEmacs it
must
build in the context of our package tree. There is no provision for
standalone builds of packages just from Lisp libraries, and none for
uploads of tarballs etc.
Our intent is to make it conform to the the XEmacs package
system in all
regards.
I can't see how it would be possible to make a build just from lisp
code--are you making the point
that it must have documentation, a manifest, etc in addition to lisp code?
And, just so I am understanding right, "none for uploads of tarballs" is
referring to a tarball that contains lisp code only, or a tarball that
does not conform to how the package system wants them?
The info page I got to from the link above says a package is a tarball,
with restrictions
on how it is made:
" 3.1 The User View
From the user's point of view, an XEmacs binary package is simply a
standard tarball (usually gzipped) containing Lisp sources, compiled
Lisp, documentation, and possibly data files or supporting executables.
The tarball is unpacked using standard tools such as GNU tar and gzip"
So I am asking if you are cautioning me from trying to upload a tarball
that is just a tarball--one that does not have the right structure? I
understand that would not be acceptable.
For single libraries, it's usually easiest to just add them to a
related existing package.
I will look for similar packages and check back to see
if others agree
or have better suggestions of where to put it.
Thanks,
Steve Mitchell
__________ Information from ESET Smart Security, version of virus signature database 6551
(20111017) __________
The message was checked by ESET Smart Security.
http://www.eset.com
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta