Romain Francoise wrote:
Sven Joachim <[EMAIL PROTECTED]> writes:
If the DOC file is identical for every architecture, yes.
Of course it is, it's just an ASCII text file with some control
characters.
The point is that it is generated (by the `make-docfile' utility) from
a file list, and t
Sven Joachim <[EMAIL PROTECTED]> writes:
> If the DOC file is identical for every architecture, yes.
Of course it is, it's just an ASCII text file with some control
characters.
> You did not mention what I think will be the biggest problem: The
> handling of add-on packages in the maintainer scr
the
make
play
I
comb
eat
by
reply
send
On
forget
have
not
dance
allow
Be
fix
need
he
fill
eat
home
watch
live
Is
spend
learn
I
speak
play
Is
sign
put
Romain Francoise wrote:
The DOC file is strongly tied to the Emacs binary as dumped during the
build, so it's recommended to ship it with the binary itself. But now
that I look into it, I see that the three files are identical:
[...]
... the file is just copied over from the -common directory w
Hubert Chan <[EMAIL PROTECTED]> writes:
> Looking at the emacs-snapshot-gtk package, it looks like the only
> reason the packages need to conflict is due to emacs-snapshot-gtk
> including:
> /usr/share/emacs/22.0.50/etc/DOC-22.0.50.1 (shouldn't this be in
> emacs-shapshot-common?)
The DOC
5 matches
Mail list logo