emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@science.uva.nl>
To: Sivaram Neelakantan <nsivaram.net@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: New structure GIT repository
Date: Sat, 29 Mar 2008 18:27:07 +0100	[thread overview]
Message-ID: <02C83C74-A659-4064-8CCF-0E8BDF82ABD7@science.uva.nl> (raw)
In-Reply-To: <usky9fp5q.fsf@gmail.com>


On Mar 29, 2008, at 5:52 PM, Sivaram Neelakantan wrote:

> Carsten Dominik <dominik@science.uva.nl> writes:
>
>> Excellent, thanks a lot!
>>
>>
>> Installing into site-lisp/org would definitely make sense, I have
>> not yet worked on the installation code, this is next.....
>>
>
> Presumably, one can also use the git downloaded lisp/ directory as-is
> (after calling make of course) to activate and use org mode?

Yes, if you are a single user who wants to stay up-to-date with the
bleeding edge development, this is a very good method.

Still, the makefile has an "install" target, and that should
do something useful for people who want to install the package,
maybe for a group of users.

> I prefer to use the git working copy (if it can be called that) folder
> as the location of the package instead of installing it before use.
>
>
> One minor bug report;
>
> Makefile does not generate the info file upon calling make.  One has
> to run
>
> make info
>
> to generate it.  Can this default behaviour be changed to generate the
> info file upon calling make?

No, because the danger is too high that systems do not have the tools  
in place
to correctly create the info file.  And the same Makefile is used in the
distribution (zip and tar) files, which contain the ready info file.

I think from a git user I can ask this extra step.  I will make is so  
that

make all

will also make the info file, ok?

- Carsten

  reply	other threads:[~2008-03-29 17:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28  9:30 New structure GIT repository Carsten Dominik
2008-03-28 12:20 ` Thomas Baumann
2008-03-28 12:32   ` Carsten Dominik
2008-03-29 16:52     ` Sivaram Neelakantan
2008-03-29 17:27       ` Carsten Dominik [this message]
2008-03-29 17:38         ` Sivaram Neelakantan
2008-03-29 16:47 ` Sivaram Neelakantan

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=02C83C74-A659-4064-8CCF-0E8BDF82ABD7@science.uva.nl \
    --to=dominik@science.uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=nsivaram.net@gmail.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 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).