Build a package yourself
[I'm CC'ing XEmacs beta as this seems relevant]
Hm, my tm scripts are in xemacs-21.0-b57/lib-src/, not somewhere in
xemacs-packages/... Anyway.
With the latest packages and the latest beta they are in
xemacs-packages/lib-src
Note that both the package layout and the package tools changed quite
a lot in the lat weeks.
c. No split. Put fonts into xemacs-packages/etc/x-symbol/pcf/
or xemacs-packages/pcf/x-symbol/ ?
xemacs-packages/etc/x-symbol/pcf
(2) Are there copyright problems with the xbm files in
XEmacs-20.4/etc/frame-icon/? (They are not in XEmacs-21.0
anymore.) Or can I move this into my distribution? I guess, dir
etc/ would be the right choice.
They are in the frame-icon package now. Search them using locate-data-*
(3) I would be nice to have a default directory name for
executables
which is at least somewhat consistent with the package system.
What do you think of using
lib/xemacs/xemacs-packages/lib/lib-src/CONFIGURATION-NAME/x-symbol/
Any better idea?
I guess you'll have to contact Steve about this. Currently I think it
would be illegal for a packge to ave architecture dependent files.
Hm. Aren't these infos availables directly?
No unless you count
http://cvs.xemacs.org/cgi-bin/cvswebp/XEmacs.rules?rev=1.12
For a simple example with data files:
http://cvs.xemacs.org/cgi-bin/cvswebp/oa/frame-icon/Makefile?rev=1.6
For a more complicated example
http://cvs.xemacs.org/cgi-bin/cvswebp/comm/gnus/Makefile?rev=1.35
http://cvs.xemacs.org/cgi-bin/cvswebp/wp/auctex/Makefile?rev=1.15
I guess I'll wait that
they will make their way to the normal XEmacs (21.0-pre) distribution
before I install a new cvs here, get used to it and XEmacs cvs, and
actually find the info...
I am afraid the CVS examples are the only documentation there is
currently.
Jan