From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Bundling GNU ELPA packages Date: Sat, 08 Nov 2014 10:23:06 -0500 Message-ID: References: <877fz8ktio.fsf@Rainer.invalid> <87y4rm6ecp.fsf@Rainer.invalid> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1415460225 18623 80.91.229.3 (8 Nov 2014 15:23:45 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 8 Nov 2014 15:23:45 +0000 (UTC) Cc: emacs-devel@gnu.org To: Achim Gratz Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Nov 08 16:23:36 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Xn7rT-00049y-Ui for ged-emacs-devel@m.gmane.org; Sat, 08 Nov 2014 16:23:36 +0100 Original-Received: from localhost ([::1]:36100 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xn7rT-0003oo-ER for ged-emacs-devel@m.gmane.org; Sat, 08 Nov 2014 10:23:35 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:47896) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xn7r9-0003m1-FM for emacs-devel@gnu.org; Sat, 08 Nov 2014 10:23:23 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xn7r1-0006qd-SJ for emacs-devel@gnu.org; Sat, 08 Nov 2014 10:23:15 -0500 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181]:43417) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xn7r1-0006qY-Og for emacs-devel@gnu.org; Sat, 08 Nov 2014 10:23:07 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Au4MAOatTlRLd+sd/2dsb2JhbABcgw6DYoZ+y1MEAgKBHBcBAXyEAwEBAwFWIwULCw4mEhQYDSSISwnLcgEBAQEGAQEBAR6RCAeESwWLZJMujV6FMIFvgXyCGh+CegEBAQ X-IPAS-Result: Au4MAOatTlRLd+sd/2dsb2JhbABcgw6DYoZ+y1MEAgKBHBcBAXyEAwEBAwFWIwULCw4mEhQYDSSISwnLcgEBAQEGAQEBAR6RCAeESwWLZJMujV6FMIFvgXyCGh+CegEBAQ X-IronPort-AV: E=Sophos;i="5.04,797,1406606400"; d="scan'208";a="96277702" Original-Received: from 75-119-235-29.dsl.teksavvy.com (HELO pastel.home) ([75.119.235.29]) by ironport2-out.teksavvy.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 08 Nov 2014 10:23:07 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id BC5D17CFA; Sat, 8 Nov 2014 10:23:06 -0500 (EST) In-Reply-To: <87y4rm6ecp.fsf@Rainer.invalid> (Achim Gratz's message of "Fri, 07 Nov 2014 19:43:34 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.181 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:176574 Archived-At: >> While there is no UI for it, package.el can definitely handle >> site-wide packages: just add the corresponding directory to >> package-directory-list. And /usr/local/share/emacs/site-lisp/elpa is >> included in there by default. > That might take care of adding a package into site-lisp, but unless I'm > mistaken there is no obvious way for the user to "delete" such a package > (unless he's got write access to site-lisp) Indeed, just like she can't "delete" a package that's bundled with Emacs. The assumption is that installing a package is "harmless" and if that's not the case, it's a bug in the package rather than a failure of the package manager. Tho, I think you can also prevent activation of a package via package-pinned-packages (i.e. pinning to version that doesn't exist). > or even just chose a different version. Yes you can fiddle with the > data structures, but that is too error-prone, I'd think. If multiple versions of the same package are installed (that can also happen in the user's own ~/.emacs.d/elpa), package.el should only activate the latest version, and if that's not the right one, the user can pick the one she wants with package-pinned-packages. At least that's the theory. This part of the code hasn't really been tested, AFAIK. > A user needs to be able to update the packages she added, while the > site administrator needs to be able to do the same for the site > collection, independently of each other. Indeed. And AFAIK the current code should behave correctly in this respect. Stefan