Re: Building emacs with and without X -- packaging question.

[Rob Browning <rlb@defaultvalue.org>]

Richard Stallman <rms@gnu.org> writes:

> The difference in etc/fns-* is easy to explain.  That file is made
> based on load-history, from whichever files were actually loaded.
>
> It would take some work to be able to make the fns file invariant.
> How important is it for us to do that?

Not sure.  The original motivation was a desire to be able to
distribute emacs21 and emacs21-nox packages, and so I was trying to
figure out if I could make these packages coexist peacefully, or if
I'd need them to conflict/replace each other.  If all the files are
the same except for the executables, then there's no problem, or if
there are a few files with different names or different fs locations
that each binary knows how to find (say fns-21.2.1.el and
fns-21.2.1-nox.el), then there's no problem.  Otherwise I'll need to
make the packages conflict/replace each other, or something similar.

> I can't see an explanation for the variance in cus-load.el.
> There is nothing in cus-dep.el or lisp/Makefile.in that ought
> to be affected by whether Emacs is built for X.
> Can you debug why it doesn't see scroll-bar.el in one case?

Sure I can try.  I presume you're talking about this diff:

  -(put 'frames 'custom-loads '( "desktop" "ediff-wind" "faces" "frame" "imenu" "menu-bar" "rsz-mini" "scroll-bar" "two-column"))
  +(put 'frames 'custom-loads '( "desktop" "ediff-wind" "faces" "frame" "imenu" "menu-bar" "rsz-mini" "two-column"))

Is this one related, or likely something else?

  -(custom-put-if-not 'gnus-article-x-face-command 'custom-version "21.1")
  -(custom-put-if-not 'gnus-article-x-face-command 'standard-value t)

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C  64AE 78FE E5FE F0CB A0AD