From: emacs18@gmail.com (Richard Y. Kim)
To: "T.F. Torrey" <tftorrey@tftorrey.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bleeding edge in elpa
Date: Mon, 09 Mar 2015 19:01:45 -0700 [thread overview]
Message-ID: <qtmtwxtsj92.fsf@gmail.com> (raw)
In-Reply-To: <871tkyvd7t.fsf@jack.tftorrey.com> (T. F. Torrey's message of "Mon, 09 Mar 2015 00:31:34 -0700")
tftorrey@tftorrey.com (T.F. Torrey) writes:
> I wonder how much effort it would take to copy onto my own machine the
> scripts on the server that package the git maint version into an ELPA
> version, and modify them to package master instead. Probably not much.
The shell script below is what I use to create my own org-plus-contrib
ELPA package.
Rather than relying on elpa.gnu.org, melpa.org, orgmode.org/elpa, etc.,
I've been creating my own packages over the past year or so. This way I
know exactly which packages are installed in not only my emacs, but my
colleagues who use my packages. So far this has worked out great for
me.
#!/bin/sh
# This script builds org-plus-contrib-YYYYMMDD.tar ELPA package from the git
# clone of org-mode.
if [ ! -f mk/server.mk ]; then
echo "Current directory must be org-mode root directory"
exit 1
fi
# Where to install the tarballs
SERVROOT=$HOME/public_html/elpa/orgmode
# server.mk has the elpaplus makefile target
echo " include mk/server.mk" >> Makefile
make SERVROOT=$SERVROOT elpaplus elpaplus-up
# Undo the change made above
git checkout Makefile
rm -f archive-contents
# $SERVROOT/org-plus-contrib-YYYYMMDD.tar
# should now be created with today as value of YYYYMMDD.
next prev parent reply other threads:[~2015-03-10 2:01 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-07 14:36 Bleeding edge in elpa Nikolai Weibull
2015-03-07 14:47 ` Xavier Maillard
2015-03-07 16:09 ` Nikolai Weibull
2015-03-08 5:48 ` Xavier Maillard
2015-03-09 9:08 ` Sebastien Vauban
2015-03-09 16:24 ` T.F. Torrey
2015-03-07 15:40 ` Grant Rettke
2015-03-07 21:44 ` T.F. Torrey
2015-03-08 1:32 ` Nicolas Girard
2015-03-08 14:17 ` Aaron Ecay
2015-03-08 17:24 ` Nikolai Weibull
2015-03-08 17:59 ` Achim Gratz
2015-03-08 18:34 ` Nikolai Weibull
2015-03-08 18:59 ` Rasmus
2015-03-09 6:48 ` T.F. Torrey
2015-03-10 1:57 ` Aaron Ecay
2015-03-10 21:30 ` T.F. Torrey
2015-03-11 2:51 ` Aaron Ecay
2015-03-11 19:18 ` T.F. Torrey
2015-03-11 19:59 ` Nick Dokos
2015-03-09 7:53 ` T.F. Torrey
2015-03-09 18:24 ` Achim Gratz
2015-03-09 19:21 ` T.F. Torrey
2015-03-10 11:01 ` Alexis
2015-03-10 15:21 ` Grant Rettke
2015-03-08 18:09 ` T.F. Torrey
2015-03-08 19:57 ` Rasmus
2015-03-08 20:20 ` Achim Gratz
2015-03-08 20:27 ` Rasmus
2015-03-08 20:36 ` Achim Gratz
2015-03-09 8:13 ` T.F. Torrey
2015-03-09 7:31 ` T.F. Torrey
2015-03-10 2:01 ` Richard Y. Kim [this message]
2015-03-10 6:29 ` Achim Gratz
2015-03-10 21:21 ` T.F. Torrey
2015-03-10 20:20 ` T.F. Torrey
2015-08-05 0:00 ` Bastien Guerry
2015-03-10 10:51 ` Steinar Bang
2015-03-10 17:11 ` 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=qtmtwxtsj92.fsf@gmail.com \
--to=emacs18@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tftorrey@tftorrey.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).