emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: Add version header to org.el
Date: Wed, 19 Aug 2015 22:11:00 +0200	[thread overview]
Message-ID: <87oai3f38r.fsf@gmx.us> (raw)
In-Reply-To: 87d1yk8owr.fsf@Rainer.invalid

Achim Gratz <Stromeko@nexgo.de> writes:

> Rasmus writes:
>>>> Is there any issues with adding a version header to org.el in maint and
>>>> master?
>>>
>>> I don't think so. It may require to update README_maintainer
>>> accordingly.
>>
>> Done.
>
> Please revert that change.  It's messing with the version numbers on
> ELPA since (as I suspected) the idea of using the version from the
> header comments in the (main) package file is half-baked.

Feel free to do so.

> Since it doesn't appear that there'll be a proper build environment for
> ELPA packages anytime soon, the only way out is to generate org.el.  We
> could do it just for ELPA, although I suggest we go ahead and do it
> across the board.  We can get rid of org-version on the way and put all
> the headers someone wants there as well.  From the new, generated org.el
> we can then require whatever the contents of org.el moves to.

If the ELPA buildbot has sed wouldn't it just be easier to change

   Version: VER

to 

   Version: VER-HASH

Where HASH is whatever it is that needs to be added.

Rasmus

-- 
If you can mix business and politics wonderful things can happen!

  parent reply	other threads:[~2015-08-19 20:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-13 23:23 Add version header to org.el Rasmus
2015-08-13 23:30 ` Nicolas Goaziou
2015-08-14  0:10   ` Rasmus
2015-08-18 17:52     ` Achim Gratz
2015-08-18 22:42       ` Bastien
2015-08-19  4:58         ` Achim Gratz
2015-08-19 20:11       ` Rasmus [this message]
2015-08-21 20:38       ` Rasmus
2015-08-21 20:58         ` Achim Gratz
2015-08-14  4:28 ` Achim Gratz
2015-08-14  9:26   ` Rasmus
2015-08-14 18:34     ` Achim Gratz

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=87oai3f38r.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --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).