unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: Keeping an ELPA checkout
Date: Mon, 28 Mar 2011 13:38:15 -0500	[thread overview]
Message-ID: <87tyenks4o.fsf@lifelogs.com> (raw)
In-Reply-To: jwvipv6rdoz.fsf-monnier+emacs@gnu.org

On Fri, 25 Mar 2011 19:20:37 -0400 Stefan Monnier <monnier@iro.umontreal.ca> wrote: 

SM> I know, but I don't think there's any fundamental good reason why we
SM> can't tweak emacs/lisp/Makefile.in so that it gets things to work.

>> They are packages, that's a great reason :)  Yeah, you can do it, but
>> it's going to break sooner or later.  I like Chong's approach better
>> than tweaking things.

>> Also, isn't it better to put the rules inside the GNU ELPA (thus the
>> "elpa" branch) than inside Emacs' lisp/Makefile.in, as Chong suggested?

SM> Where they go doesn't matter much, yes..  The important part is to be
SM> able to use them in-place and have them all activated from a single
SM> place with "bzr up; make".

OK.  So who's going to do the work?  And can you summarize what you're
asking for after this discussion?

Ted




  reply	other threads:[~2011-03-28 18:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-24 22:21 Keeping an ELPA checkout Stefan Monnier
2011-03-25  8:19 ` Reiner Steib
2011-03-25 21:09   ` Stefan Monnier
2011-03-25 14:46 ` Ted Zlatanov
2011-03-25 19:52   ` Stefan Monnier
2011-03-25 20:53     ` Ted Zlatanov
2011-03-25 21:06       ` Chong Yidong
2011-03-25 21:16         ` Ted Zlatanov
2011-03-26 19:31           ` Tom Tromey
2011-03-25 21:12       ` Stefan Monnier
2011-03-25 22:02         ` Ted Zlatanov
2011-03-25 23:20           ` Stefan Monnier
2011-03-28 18:38             ` Ted Zlatanov [this message]
2011-03-29  1:16               ` Stefan Monnier
2011-03-29 15:06                 ` Ted Zlatanov
2011-03-29 21:16                   ` Stefan Monnier
2011-03-30 13:28                     ` Ted Zlatanov
2011-03-30 21:29                       ` Stefan Monnier

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87tyenks4o.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=emacs-devel@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.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).