From: Bastien <bzg@altern.org>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: difficulty installing 7.9 with the new build system: org-version not informative
Date: Sun, 26 Aug 2012 09:45:54 +0200 [thread overview]
Message-ID: <878vd2nlef.fsf@altern.org> (raw)
In-Reply-To: <874nnqjfgy.fsf@Rainer.invalid> (Achim Gratz's message of "Sun, 26 Aug 2012 09:10:37 +0200")
Achim Gratz <Stromeko@nexgo.de> writes:
> Bastien writes:
>>> I'll add
>>> a file to the tarball that just defines these two variables and include
>>> that when absolutely no version is defined.
>>
>> Can't we just have this in default.mk? Do we need yet another file?
>
> That would mean I'd have to change default.mk while building the tarball
> and then change it back afterwards. There's no way I can make that
> completely foolproof, so I'll rather just generate a file specifically
> for the tarball that I can throw away any time without having to keep
> state.
Let me know if I understand correctly: that's because you don't want
default.mk to contain a manually inserted ORGVERSION variable, right?
Otherwise I don't see the problem with having a fallback ORGVERSION
variable in default.mk (which I'll happily insert manually, to have a
taste of the Good Old Days, when (defconst org-version "...") was
still in org.el... :)
--
Bastien
prev parent reply other threads:[~2012-08-26 7:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-25 13:40 difficulty installing 7.9 with the new build system: org-version not informative Brian van den Broek
2012-08-25 17:24 ` Achim Gratz
2012-08-25 19:08 ` Brian van den Broek
2012-08-25 20:03 ` Achim Gratz
2012-08-25 20:12 ` Bastien
2012-08-25 20:16 ` Brian van den Broek
2012-08-25 20:18 ` Achim Gratz
2012-08-25 20:23 ` Bastien
2012-08-26 7:10 ` Achim Gratz
2012-08-26 7:45 ` Bastien [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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878vd2nlef.fsf@altern.org \
--to=bzg@altern.org \
--cc=Stromeko@nexgo.de \
--cc=emacs-orgmode@gnu.org \
/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/org-mode.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).