unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Peter Dyballa <Peter_Dyballa@Freenet.DE>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-pretest-bug@gnu.org, Sven Joachim <svenjoac@gmx.de>
Subject: Re: 23.0.60; etc/DOC-${version}.buildnumber
Date: Sat, 12 Apr 2008 20:55:57 +0200	[thread overview]
Message-ID: <560E9570-DDB2-4008-9E47-CEB2E631B783@Freenet.DE> (raw)
In-Reply-To: <uiqyn7zqz.fsf@gnu.org>


Am 12.04.2008 um 19:24 schrieb Eli Zaretskii:
> Maybe I completely misunderstand the issue at hand: are we talking
> about files in the build directory or in the install directory?
> ("make clean" is relevant to the former, not the latter.)

About both. Because the DOC files in the build tree are also installed.

>
> If Peter and you are talking about the build directory, then the
> previous DOC should probably be removed, but do we really want the
> build number NOT to be incremented anyway?

I want to have control over this mechanism. Usually I want to have  
only one build number version (and I don't want to waste time by re- 
configuring again after a 'make distclean' or such). Because when it  
happens that I start over, none of the installed superfluous DOC  
files and Emacs versions are de-installed. This worked until some day  
in winter, in February, I think. Then the etc/DOC-$ 
{version}.buildnumber<s> files were saved and new ones with  
incremented build numbers were created, and sometimes also installed  
when I did not pay attention. This seems to have changed recently (I  
am still waiting for a 'make bootstrap' to finish) ...

--
Greetings

   Pete

Behold the warranty ... the bold print giveth and the fine print  
taketh away.






      parent reply	other threads:[~2008-04-12 18:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-12 12:00 23.0.60; etc/DOC-${version}.buildnumber Peter Dyballa
2008-04-12 13:10 ` Eli Zaretskii
2008-04-12 15:14   ` Peter Dyballa
2008-04-12 16:43     ` Eli Zaretskii
2008-04-12 19:41       ` Peter Dyballa
2008-04-12 16:32   ` Sven Joachim
2008-04-12 17:24     ` Eli Zaretskii
2008-04-12 17:54       ` Sven Joachim
2008-04-12 18:57         ` Eli Zaretskii
2008-04-12 19:00           ` Peter Dyballa
2008-04-12 20:30             ` Eli Zaretskii
2008-04-12 20:59               ` Peter Dyballa
2008-04-13  3:18                 ` Eli Zaretskii
2008-04-13  8:38                   ` Peter Dyballa
2008-04-13 14:07                     ` Eli Zaretskii
2008-04-12 20:49           ` Stephen J. Turnbull
2008-04-12 21:04             ` Peter Dyballa
2008-04-12 23:58               ` Stephen J. Turnbull
2008-04-12 19:21         ` Stefan Monnier
2008-04-12 18:55       ` Peter Dyballa [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=560E9570-DDB2-4008-9E47-CEB2E631B783@Freenet.DE \
    --to=peter_dyballa@freenet.de \
    --cc=eliz@gnu.org \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=svenjoac@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).