From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Andreas Schwab <schwab@linux-m68k.org>, emacs-devel@gnu.org
Subject: Re: Git version of ELPA
Date: Wed, 14 Aug 2013 11:30:23 -0400 [thread overview]
Message-ID: <jwvy584coso.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <520B4B29.8030201@yandex.ru> (Dmitry Gutov's message of "Wed, 14 Aug 2013 12:17:29 +0300")
> 2) If packages/js2-mode and git@github.com:mooz/js2-mode.git differ in files
> they contain, I imagine we'll have more errors or conflicts to deal with.
Yes and no: the "push" would simply force the github version to have
the same content as the elpa version. No conflict, but an undesirable
outcome, so you end up having to do it somewhat by hand (you can use
"git subtree split" to help, but there's still a manual intervention
needed).
>> In any case it's the responsibility of the package's maintainer to feed
>> elpa changes back to the external branch, if any.
> Maybe so. But 'git subtree' seems to make this less painful, as long as ELPA
> doesn't go deliberately out of sync.
Yes. The elpa-diffs email as well (a copy is sent to the maintainer).
>>> 2) Can we handle having README.md (and probably other formats),
>> Yes. Patches welcome (tho you might like to wait before the new Git
>> repository is in place, since the code is being rewritten as we speak).
> If we're okay with showing non-preprocessed Markdown, Org and similar files
> as plain text, that should be easy. Markdown reads fine that way, at least.
Hopefully we can do better than that, but as a first step, yes, that's
definitely fine.
>> Currently, you can have extra (ignored) files only for singlefile
>> packages. Multifile packages will package up whatever is present.
>> But it should be easy to add some way to list files that should be
>> skipped. IOW, same as above "patch is welcome, tho you might like to
>> wait a bit".
> I'd welcome a suggestion for the exact mechanism.
A simple solution is to not remove those files from the `elpa' branch.
I.e. consider it as a "local change". It might lead to spurious
conflicts when merging, tho.
> List them in a file called .elpa-includes'?
I'd rather have a list of exclusions than a list of inclusions, but
other than that I guess that'd be right. So we could easily handle
a list of exclusions by passing the list to "tar".
Stefan
next prev parent reply other threads:[~2013-08-14 15:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 17:54 Git version of ELPA Stefan Monnier
2013-08-02 10:30 ` Andreas Schwab
2013-08-02 17:22 ` Stefan Monnier
2013-08-02 21:32 ` Andreas Schwab
2013-08-03 4:28 ` Stefan Monnier
2013-08-03 8:19 ` Eli Zaretskii
2013-08-11 22:08 ` Dmitry Gutov
2013-08-12 1:10 ` Stefan Monnier
2013-08-12 2:04 ` Stefan Monnier
2013-08-12 6:17 ` Dmitry Gutov
2013-08-12 15:24 ` Stefan Monnier
2013-08-12 16:23 ` Dmitry Gutov
2013-08-13 1:42 ` Stefan Monnier
2013-08-14 9:17 ` Dmitry Gutov
2013-08-14 15:30 ` Stefan Monnier [this message]
2013-08-14 16:48 ` Dmitry Gutov
2013-08-14 19:02 ` Stefan Monnier
2013-08-14 20:46 ` Dmitry Gutov
2013-08-16 23:04 ` Dmitry Gutov
2013-08-15 4:08 ` Stephen J. Turnbull
2013-08-15 18:38 ` Achim Gratz
2013-08-17 0:59 ` Dmitry Gutov
2013-08-13 5:16 ` Achim Gratz
2013-08-14 9:46 ` Dmitry Gutov
2013-08-14 18:13 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvy584coso.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=schwab@linux-m68k.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.