Hi,
Jambunathan K writes:
[...]
>
> Part-2
> ==
>
> Downloaded and installed org-20101020.tar. The installation process
> reported some compile time warnings. See down below.
>
I've fixed two of the babel related compile time warnings. I think that
in general releases will be warning free
Wonderful Bastien.
Part-1
==
Did you forget to upload http://orgmode.org/pkg/daily/archive-contents?
Once this is done orgmode.org could be used as an ELPA repo in and of
itself. I am attaching a sample archive-contents for your ready
reference.
Part-2
==
Downloaded and installed org-
Hi Jambunathan,
thanks for your work on the ELPA-compatible Makefile.
Jambunathan K writes:
> One could host N latest snapshots and expunge the rest. The snapshots
> could be published either daily or weekly etc etc. This could be hooked
> to existing cron job.
This is now the case - see this
Carsten
Reworked the changes based on your feedback. Customize to your tastes.
Jambunathan K.
>From 1121461037e0308054afeabf8c67bd1a568dd9b1 Mon Sep 17 00:00:00 2001
From: Jambunathan K
Date: Tue, 5 Oct 2010 15:33:08 +0530
Subject: [PATCH] Support for elpa-compatible tarballs
* Makefile (pkg
On Oct 4, 2010, at 8:23 PM, Jambunathan K wrote:
Carsten Dominik writes:
Ji Jambunathan,
there is something in your Makefile patch I do not understand:
X @@ -325,6 +328,14 @@ distfile:
X zip -r org-$(TAG).zip org-$(TAG)
X gtar zcvf org-$(TAG).tar.gz org-$(TAG)
X
X +elpa:
Carsten Dominik writes:
> Ji Jambunathan,
>
> there is something in your Makefile patch I do not understand:
>
>>
>> X @@ -325,6 +328,14 @@ distfile:
>> Xzip -r org-$(TAG).zip org-$(TAG)
>> Xgtar zcvf org-$(TAG).tar.gz org-$(TAG)
>> X
>> X +elpa: install-info
>
> Why are you saying th
Hello Carsten
> Ji Jambunathan,
>
> there is something in your Makefile patch I do not understand:
>
>>
>> X @@ -325,6 +328,14 @@ distfile:
>> Xzip -r org-$(TAG).zip org-$(TAG)
>> Xgtar zcvf org-$(TAG).tar.gz org-$(TAG)
>> X
>> X +elpa: install-info
>
> Why are you saying the elpa is
Hi Jambunathan,
Would you mind re-sending your original Makefile patch un-commented so
that it will be captured by the patchwork system, and dropped into the
org-mode development review process?
Thanks -- Eric
"Eric Schulte" writes:
> Hi Jambunathan,
>
> Jambunathan K writes:
>
>> Hello Eric
Ji Jambunathan,
there is something in your Makefile patch I do not understand:
X @@ -325,6 +328,14 @@ distfile:
X zip -r org-$(TAG).zip org-$(TAG)
X gtar zcvf org-$(TAG).tar.gz org-$(TAG)
X
X +elpa:install-info
Why are you saying the elpa is dependent on install-info?
-
Hi Jambunathan,
Jambunathan K writes:
> Hello Eric
>
> "Eric Schulte" writes:
>> Jambunathan K writes:
>>
[...]
>>>
>>> ELPA Server-side setup:
>>>
>>
>> I think we can ignore the server-side setup, since that should be
>> handled by the elpa server at tromney or gnu.org. Is this correct?
>>
Hello Eric
"Eric Schulte" writes:
> Jambunathan K writes:
>
>> I managed to create an elpa compatible tar for orgmode. Recording here
>> what I did in the hope that it will be useful.
>>
>> Creating ELPA-compatible tar:
>>
>> 1. Add the enclosed changes to Makefile.
>> 2. Create an ELPA-compati
Jambunathan K writes:
> I managed to create an elpa compatible tar for orgmode. Recording here
> what I did in the hope that it will be useful.
>
> Creating ELPA-compatible tar:
>
> 1. Add the enclosed changes to Makefile.
> 2. Create an ELPA-compatible tarfile with
>$ make TAG=20100930 elpa
> This means that a restart of Emacs is necessary for the new changes to
> take effect. I am not sure whether it is intended. But this behaviour
> could surprise the user.
When using ELPA, I always restart emacs. I got into that habit when
installing many code packages (like the ruby/rails package
I managed to create an elpa compatible tar for orgmode. Recording here
what I did in the hope that it will be useful.
Creating ELPA-compatible tar:
1. Add the enclosed changes to Makefile.
2. Create an ELPA-compatible tarfile with
$ make TAG=20100930 elpa
3. Copy the generated org-20100930.t
14 matches
Mail list logo
