emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Tim O'Callaghan" <timo@dspsrv.com>
To: Bernt Hansen <bernt@norang.ca>
Cc: org-mode <emacs-orgmode@gnu.org>
Subject: Re: org-install.el in Emacs probably should be removed
Date: Tue, 24 Feb 2009 16:38:00 +0100	[thread overview]
Message-ID: <3d6808890902240738u8f5e891mc32308130cc9fc44@mail.gmail.com> (raw)
In-Reply-To: <87vdrb9hvk.fsf@gollum.intra.norang.ca>

[-- Attachment #1: Type: text/plain, Size: 2000 bytes --]

On 16/02/2009, Bernt Hansen <bernt@norang.ca> wrote:
> Carsten Dominik <dominik@science.uva.nl> writes:
>
>  > On Feb 15, 2009, at 11:18 PM, Tim O'Callaghan wrote:
>  >
>
> >> The usage of org-install has the pre-requisite of having to compile
>  >> the org.el files. This is no use to people like myself, who want to
>  >> use the same .el files in XEmacs and Emacs due to incompatible .elc
>  >> problems. Its also no use to people who do no have a build system or
>  >> make binary installed e.g. windows users, locked down linux/unix
>  >> systems etc.
>  >>
>  >> How about adding a skeleton org-install.el that gets overwritten by
>  >> the make?
>  >
>  > org-install.el is part of the distribution tar and zip files.
>  > I cannot include it into the git repo because the git people tell
>  > me that it is a bad idea to keep a product file under git
>  > control (Bernt?).
>
>
> The main reason this is a bad idea in git master branch is that the file
>  gets automatic changes on different systems and looks modified after
>  each time you run make.  This file gets in the way of other (real)
>  changes since git thinks the working tree is dirty and prevents changing
>  branches, rebasing, or merging with a dirty tree.  The contents of the
>  org-install.el file are uninteresting and really does not belong in the
>  tracked files for the project since it is a product of the build
>  procedure.
>
>  If you want a skeleton org-install.el in the tar/zip files then you
>  probably should generate that when producing the tar/zip files.
>
>
>  -Bernt
>

That is a fair point, its usually counter productive to put a build
product under revision control.

So for the sake of those looking for an example one, you'll find a
generated example attached, for V6.23b

I wonder if it is possible to implement a mechanism to check the
'freshness' of the org-install? say embedding the org-version number
it was created with, and org checking to see if it is compatible, or
needs updating?

Tim.

[-- Attachment #2: example-org-install.el --]
[-- Type: application/emacs-lisp, Size: 39040 bytes --]

[-- Attachment #3: Type: text/plain, Size: 204 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

      reply	other threads:[~2009-02-24 15:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-15  7:50 org-install.el in Emacs probably should be removed Leo
2009-02-15 20:03 ` Carsten Dominik
2009-02-15 22:18   ` Tim O'Callaghan
2009-02-15 22:40     ` Carsten Dominik
2009-02-16  3:32       ` Bernt Hansen
2009-02-24 15:38         ` Tim O'Callaghan [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=3d6808890902240738u8f5e891mc32308130cc9fc44@mail.gmail.com \
    --to=timo@dspsrv.com \
    --cc=bernt@norang.ca \
    --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).