Achim Gratz writes:
> I went ahead and moved the schema dir from contrib to etc and adapted
> the Makefile to install it.
Now pushed to my Makefile fork after testing it on Win7 (and rebased
again to current master).
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>
Rebased to 7.8.03.
Achim Gratz writes:
> I'm uncertain about the integration of the ODT exporter (although it
> works on my machine): it seems that the schema files should reside in
> etc/schema (and ETCDIR should include schema on install)?
I went ahead and moved the schema dir from contrib t
I've implemented a few improvements in my fork that should take care of
most issues raised in recent discussions:
- default target is now "all" instead of "help"
- make does not complain when not inside a Git tree
- all installations prefixed with $(DESTDIR) to allow for staged
installation
Am 26.12.2011 05:58, schrieb Takaaki ISHIKAWA:
I think many Org users are familiar to the previous installation
procedure by "make" not "make all", and some users wrote it in their
blog, Org manual [*1] too.
Yes, the manual would need to be changed in any case. The semantics of
some targets
Hi. Achim,
Thank you for your kind explanations.
I learned a lot from you :)
> I opted for this behaviour to align more closely to GNU convention and to
> avoid any surprising behaviour, but it is easy to make the default target
> "all" instead of "help".
I think many Org users are familiar to
[sorry if you get this twice
- GMane seems to have trouble sending lately]
Am 22.12.2011 16:06, schrieb Takaaki ISHIKAWA:
I think "make" and "make all" have the same effect usually.
Often they do, but GNU says that a simple "make" should behave like
"make help". I think this is appropriate
Hi Achim and Takaaki,
Takaaki ISHIKAWA writes:
> I think "make" and "make all" have the same effect usually.
> In the new Makefile of org-mode, however, "make" is used
> for displaying options of make command.
> Is this familiar to all?
>
> For example, GNU Emacs doesn't require "make all", jus
Dear Achim,
Hi. Thank you for your comment and great work on refactoring Makefile.
> Just "make" doesn't work anymore (it displays a usage section to conform to
> GNU convention), you'll need "make all". This now implies a "make clean", so
> you'll normally don't need this as an extra step any
Am 21.12.2011 19:47, schrieb Bastien:
Things are fine here, you should be safe. The purpose of
the test is to make sure `make&& make install' do the right
thing in various setups.
Actually, that should be
make all && make install
or (under Unixoid system and running as a normal user):
mak
Am 22.12.2011 02:35, schrieb Takaaki ISHIKAWA:
1. When I just type "make", I find a fatal error message:
Not a git repository (or any parent up to mount parent )
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Just "make" doesn't work anymore (it displays a usag
Hi Bastien,
I have tried to install the new package in my clean VM of Suse 12.1.
I'd like to report my install experience.
> http://orgmode.org/Org-7.8.03-TestMakefile.zip
1. When I just type "make", I find a fatal error message:
Not a git repository (or any parent up to mount parent )
Stopp
Dear all,
I've now bundled Achim's new Makefile in these archives:
http://orgmode.org/Org-7.8.03-TestMakefile.tar.gz
http://orgmode.org/Org-7.8.03-TestMakefile.zip
Can some of you test the make procedures from there?
Things are fine here, you should be safe. The purpose of
the test is to
12 matches
Mail list logo
