all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: Sebastien Vauban <sva-news@mygooglest.com>,
	Eli Zaretskii <eliz@gnu.org>,
	Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: Emacs trunk binary on Dropbox
Date: Wed, 02 Oct 2013 12:00:57 +0900	[thread overview]
Message-ID: <87vc1gqsuu.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <CAH8Pv0gEon5S+CY6y_Exa5+d7azJGbKujdLTGRHqGJqWgtML4g@mail.gmail.com>

Dani Moncayo writes:

 > It would be nice if I could specify the bzr revno manually, for
 > example as a parameter to "configure" or "make", because having to
 > keep using bzr just for this little thing would also be too bad.

I don't own the code so won't quote it here, but XEmacs has a file
named "version.sh" which contains mostly static information about the
version: current major and minor, most recent patchlevel, beta status,
and something called "extra version info".  I forget how it's done (I
think it's in configure) but if hg is available, just do "hg id -i -n
>> version.sh", and then make includes that file so that the version
values are available in Make variables.  They may also be substituted
into config.h, I forget.  The latter would probably be easiest: add
a "version-extra-info" building variable to Lisp (in C), and add

#define VERSION_EXTRA_INFO @@VERSION_EXTRA_INFO@@

to config.h.in, and let configure do its thing using the bzr revision
number or revision id or both (I prefer both since people using bzr
who are off the mainline with local changes won't have useful revnos).

If you use a shell/make script, the tricky part is that it's essential
that the "extra_version_info=" line be last and unterminated with a
newline.

Presumably some similar could be done with lisp/version.el or
whatever as well.

I don't see why the maintainers would object to this, so feel free to
come up with a patch.






  parent reply	other threads:[~2013-10-02  3:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-01  7:55 Emacs trunk binary on Dropbox Sebastien Vauban
2013-10-01  8:29 ` Dani Moncayo
     [not found] ` <mailman.3202.1380616171.10748.help-gnu-emacs@gnu.org>
2013-10-01  8:46   ` Sebastien Vauban
2013-10-01  9:12     ` Dani Moncayo
2013-10-01 16:01       ` Eli Zaretskii
2013-10-01 16:08         ` Dani Moncayo
2013-10-01 16:22           ` Lennart Borgman
2013-10-01 16:36             ` Andreas Schwab
2013-10-01 17:48           ` Eli Zaretskii
2013-10-02  3:00           ` Stephen J. Turnbull [this message]
     [not found]     ` <mailman.3203.1380618754.10748.help-gnu-emacs@gnu.org>
2013-10-01  9:34       ` Sebastien Vauban
2013-10-01  9:58         ` Dani Moncayo

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

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

  git send-email \
    --in-reply-to=87vc1gqsuu.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --cc=dmoncayo@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=sva-news@mygooglest.com \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.