From: phillip.lord@russet.org.uk (Phillip Lord)
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Remove Org from Emacs repository?
Date: Tue, 20 Dec 2016 10:13:04 +0000 [thread overview]
Message-ID: <87r3526h8v.fsf@russet.org.uk> (raw)
In-Reply-To: <WM!fdb65752b64ef5461efbcb948e173a504edcf68a88cb151b38f9292793a941a33217a0cc771607f86b8962c90b171694!@mailhub-mx4.ncl.ac.uk> (Achim Gratz's message of "Mon, 19 Dec 2016 19:53:16 +0100")
Achim Gratz <Stromeko@nexgo.de> writes:
> Phillip Lord writes:
>> I think there's only a few problems, actually. package.el initialization
>> is all or nothing at the moment, and is disabled on emacs -q. Neither of
>> these would make sense if we wanted in built packages.
>
> My opinion is that unless package.el adds explicit support for
> system-level packetization decisions (i.e. for admins or distributions)
> it's not going to gain widespread support from that small, but important
> set of folks.
I think it mostly has this, in the sense that you can add packages into
admin installation locations. Although, this are disabled with emacs -Q.
> Of course the user will then have to be able to override these like
> deactivation of packages, installing different versions, etc.
Different versions you can do. Deactivation at the moment, no, although
I guess you could delete the autoloads.
> Before long it also needs to be able to cope with different package
> archives simultaneously especially when those have incompatible
> numbering schemes.
That one would be a bit harder, although you could add support for
package repositories to add their own numbering scheme by installating a
package.
>
>> It's not strictly necessary, though. The current idea is to not to use
>> packages but to, essentially, move the lisp of packages in ELPA into
>> place in the build. package.el need not be involved then.
>
> Yes I know. Which is in essence prolonging the current state of affairs
> as far as the users are concerned. If it gets things moving into the
> right direction I'll be glad. I just had hoped for some more general
> (some would say radical) solution.
Some did say radical, unfortunately.
Still, you give me encouragement. I may complete my solution after
all. Perhaps combined with a completely repackaged Emacs core.
Phil
next prev parent reply other threads:[~2016-12-20 10:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-17 22:43 Remove Org from Emacs repository? Reuben Thomas
2016-12-18 9:22 ` aaermolov
2016-12-18 13:20 ` Carsten Dominik
2016-12-18 13:59 ` Rasmus
2016-12-18 14:41 ` Greg Troxel
2016-12-18 15:53 ` Kaushal Modi
2016-12-18 17:01 ` Reuben Thomas
[not found] ` <WM!f754fa008f759b442796c83f07a493b80e9d7ae4298a54f3fabf6b50a6e8ba9da1d361e87e441eae1fe9b1deeb824e68!@mailhub-mx3.ncl.ac.uk>
2016-12-19 15:32 ` Phillip Lord
2016-12-19 15:45 ` Reuben Thomas
2016-12-18 17:11 ` Christian Moe
2016-12-18 18:46 ` Xebar Saram
2016-12-18 19:08 ` Lambda Coder
2016-12-19 18:09 ` Scott Randby
2016-12-18 19:21 ` Samuel Wales
2016-12-18 23:32 ` Reuben Thomas
2016-12-19 1:36 ` MaDhAt2r
2016-12-19 10:42 ` Achim Gratz
[not found] ` <WM!759fdf23a4a1bd7b46432ee60644e52fd7beb44781fd97109e1d38080c6611cbecaf3bf7f1ea49cdc6a1823f1a9663ec!@mailhub-mx4.ncl.ac.uk>
2016-12-19 17:14 ` Phillip Lord
2016-12-19 18:53 ` Achim Gratz
[not found] ` <WM!fdb65752b64ef5461efbcb948e173a504edcf68a88cb151b38f9292793a941a33217a0cc771607f86b8962c90b171694!@mailhub-mx4.ncl.ac.uk>
2016-12-20 10:13 ` Phillip Lord [this message]
2017-01-16 8:36 ` Erik Colson
2016-12-19 1:52 ` Eric Abrahamsen
2016-12-19 4:42 ` Maria Shinoto
2016-12-20 20:07 ` Preventing Org from being installed by elpa (was: Remove Org from Emacs repository?) Karl Voit
2016-12-21 9:47 ` Preventing Org from being installed by elpa Christian Wittern
2016-12-21 13:25 ` Karl Voit
2016-12-21 23:06 ` Christian Wittern
[not found] ` <WM!fbba205c161c2d01739b0e77a8ccc521b0d6b80e8ba4b6108c74becbbd57ccbdb4003d644b63e3c98578a5b823582b17!@mailhub-mx3.ncl.ac.uk>
2016-12-21 12:40 ` Phillip Lord
2016-12-21 13:27 ` Karl Voit
[not found] ` <WM!dd5bd1ff96755a23a0384200326165bb89b1fc0144607ae0870bc4237fe325fe903cdff298d097ecb318c066c7b3726c!@mailhub-mx1.ncl.ac.uk>
2016-12-21 14:55 ` Phillip Lord
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=87r3526h8v.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--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).