On Tue, 2002-10-22 at 13:27, Stephen J. Turnbull wrote:
drv> BTW: something boring with the packages is that when you
drv> don't want to install one, it seems that compiling it is
drv> still required.
I don't understand. If you build from the top, yes, but if you build
in the package directory (which unfortunately can fail), it should
work OK whether other packages are compiled or not.
...and if it doesn't work, you'll need to add some "indirect" REQUIRES
entries. Meaning that the package you're building doesn't need those
REQUIRES itself, but some of its real requirements do. Sigh...
Here's the patch. My oort lives in site-packages/oort-gnus, but
otherwise is a standard XEmacs Gnus hierarchy.
Hmm, now I don't understand; site-packages? Why introduce a new build
dir and not use unsupported/stephen for that? The packages built from
unsupported/ will land nicely in UNSUPPORTED_STAGING, which defaults to
${UNSUPPORTED_PACKAGES_BASE}/../../site-packages. See
unsupported/Local.rules.mk.
Be sure to set package-info.in (distribution) and Makefile (CATEGORY) to
"unsupported" and it'll work just fine. And do the other tweaks to the
files under unsupported/ too (eg. package-compile.el
(package-directory-map)).
+MANUALS = gnus message emacs-mime
[...]
+.PHONY: srckit binkit
+
+srckit:
+ @echo "You can't build a source kit for Gnus this way"
The source targets and MANUAL stuff were removed last week from the
packages tree, be sure that you're using up to date build files as
templates...
--
\/ille Skyttä
scop at
xemacs.org