From: tftorrey@tftorrey.com (T.F. Torrey)
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bleeding edge in elpa
Date: Mon, 09 Mar 2015 12:21:10 -0700 [thread overview]
Message-ID: <87pp8it1sp.fsf@jack.tftorrey.com> (raw)
In-Reply-To: <87egoym3kc.fsf@Rainer.invalid> (message from Achim Gratz on Mon, 09 Mar 2015 19:24:51 +0100)
Achim Gratz <Stromeko@nexgo.de> writes:
> The version of package manager that people most likely use today always
> choses the latest version from _any_ archive available when you update.
> You can't tell it to consider some archive more authoritative than
> another or that it should stick with whatever source archive the package
> was originally installed from.
Of course. My explanation was worded poorly, because instead of
sleeping I was wasting my time supporting someone else's request to be
able to get the latest version of Org via ELPA.
>> The current daily builds are here:
> […]
>
> That sort of contorsionist gymnastics defeats the whole point of having
> a package manager in the first place. If every package would have to do
> that we'd all end up juggling dozens of archives in our config files.
The guidance for using Org via ELPA is already to "add the
Orgmode.org/elpa archive" (paraphrased). Changing that to "add
Orgmode.org/elpa-stable for the stable version or
Orgmode.org/elpa-unstable for the bleeding edge version" is suddenly
contortionist gymnastics? Really? Compared to using git?
>> If the next version of Emacs breaks Org out of core into the GNU ELPA
>> package archive, things can be even easier: Keep the stable version in
>> the GNU package archive, and keep the unstable version in the archive on
>> the orgmode.org server.
>
> I wouldn't hold my breath. At the moment that mechanism by which to do
> that is certainly not in place and there's no agreement on what it
> should look like.
Agreement or not, something will be done. Already the mechanisms are in
place that put the maint version in both locations. The biggest
obstacle I to this that I see is that developers tend to hate the
package manager and love git.
>> (And personally, I think the "contrib" parts should either be merged
>> into the core or split into separate packages, but that's another can of
>> worms.)
>
> if you want to move things into core, clean those files up, create tests
> and get the copyrights assignmed to the FSF by their authors and propose
> their inclusion.
>
> If you want separate packages, I'm quite certain that this needs further
> modifications at least to some of the files. The current mode of
> operation is that they should be compiled together with the rest of Org
> and no checks are made if they work if installed sepaerately. Some of
> them likely do, others probably not.
Yes, either choice would be an effort.
However, there is currently the problem that some packages depend on
org, and others on org-plus-contrib, which cause both to be installed
(without some controtionist gymnastics). IMHO, the Org package at
Orgmode.org/elpa should either always include contrib, as the git
repository does, or split the contrib part into an org-contrib package
that depends on org.
All the best,
Terry
--
T.F. Torrey
next prev parent reply other threads:[~2015-03-09 19:21 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 [this message]
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
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=87pp8it1sp.fsf@jack.tftorrey.com \
--to=tftorrey@tftorrey.com \
--cc=Stromeko@nexgo.de \
--cc=emacs-orgmode@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/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).