From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Philipp Stephani Newsgroups: gmane.emacs.devel Subject: Re: Future role of ELPA Date: Sun, 21 Feb 2016 10:05:41 +0000 Message-ID: References: <87a8n20y7x.fsf@gmx.de> <87k2m60y08.fsf@mbork.pl> <871t8d26zp.fsf@gmx.de> <8760xpce7i.fsf@xsteve.at> <87vb5paxlp.fsf_-_@xsteve.at> <87h9h8bi9x.fsf@xsteve.at> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a114451d0717530052c44dc75 X-Trace: ger.gmane.org 1456049163 27089 80.91.229.3 (21 Feb 2016 10:06:03 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 21 Feb 2016 10:06:03 +0000 (UTC) To: Stefan Monnier , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Feb 21 11:06:03 2016 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 1aXQtq-0007P8-VO for ged-emacs-devel@m.gmane.org; Sun, 21 Feb 2016 11:05:59 +0100 Original-Received: from localhost ([::1]:39666 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aXQtq-0005CM-7A for ged-emacs-devel@m.gmane.org; Sun, 21 Feb 2016 05:05:58 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59942) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aXQtm-0005Bw-7m for emacs-devel@gnu.org; Sun, 21 Feb 2016 05:05:55 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aXQtl-00052w-2I for emacs-devel@gnu.org; Sun, 21 Feb 2016 05:05:54 -0500 Original-Received: from mail-wm0-x236.google.com ([2a00:1450:400c:c09::236]:35098) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aXQtk-000528-Os for emacs-devel@gnu.org; Sun, 21 Feb 2016 05:05:52 -0500 Original-Received: by mail-wm0-x236.google.com with SMTP id c200so132150360wme.0 for ; Sun, 21 Feb 2016 02:05:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-type; bh=qso7jwAMb+F6WD372hEMASVklLxrKHmCiMxcjPml/L8=; b=sx+6uJ/ANMYF6GiAnJpIrqRgCwFSYM2ZimbmzJbrH2pLM9gDSutW6pS5skAgw5yFK6 WxPxzgfg91Hb+GYUOzZPQ9KEKMIfn0EN6ZFS/5dglC16SDAYtCtCqXEQTgB/vpLxmSCS Sn7D6HjO/Le3kBr9W4sMqqczThVaN1uDpnMlHLcgriaIHPu+zqAkvzEeizYpgdLvQLMk pmI3wx2YtGnWjet8ap55W3iK/szRy6y6d5MNy8NNIDqIlrRdFP0OyrQvCXLCrNX679qD GP0iHurIkJEX7d/H6EXoMPgfyQfi1aLKiHGnvQKyVo9KqCY1/11Y6U5jqV7gYAhRXTY+ rRqg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-type; bh=qso7jwAMb+F6WD372hEMASVklLxrKHmCiMxcjPml/L8=; b=a3+6ycYYAeQwVay2vKFpLiK6Gz1A8LqnLd9Tb4fQFcXYjlcQxZIN1J7reAOlFlnBC9 ibJB8dnjtxMu6ByqUiABXGXXpwrv1vnvp5M54U+HIUjaV6GrmSr1tljCjD+8lD3yXVGp +PjMIZzJlWC+j//pN7YV89B2NASc4lKDbmoaCAPIqLgSzBwJ1Y+dq42rAwwKfatbO4cV rF0olBR2qWauybidgqD70scooZVmv8ddLW0VZV4f1weijo5z1Nczpmpv2tRLPmmMgtVv 37BcMSN3f3rBr8t0gCY7Wtf++f8fI2ONzEYREGxTYfuM3/hsb1U8JokTVIxBUUah/5rK rF6A== X-Gm-Message-State: AG10YOSDbLFuyb5sU7z8vfWkAgiVeKhi2SRWR4oEjHoym7vAEqlptRqedxr/NdIhUgOj5DdtXKRT6JCVEQcEAA== X-Received: by 10.28.51.74 with SMTP id z71mr6194174wmz.15.1456049151372; Sun, 21 Feb 2016 02:05:51 -0800 (PST) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2a00:1450:400c:c09::236 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:200367 Archived-At: --001a114451d0717530052c44dc75 Content-Type: text/plain; charset=UTF-8 Stefan Monnier schrieb am So., 21. Feb. 2016 um 03:19 Uhr: > > 1. Not only emacs provides a package manager. Linux distributions also > > provide some packages. Not sure if this is a good idea. > > The same situation is e.g. for python. You can use pip to install > > packages. And there are python packages provided by distributions. > > Some people prefer OS packages, some prefer the native package > manager. > > Not sure what to do about this situation. > > It's easy to make a .deb package which installs an Elisp package in the > way package.el would have installed it (but with global scope). > > The two aren't 100% equivalent (upgrading/removing a dpkg-installed > package via package.el won't do the right thing), but the Debian > packages can easily do better than what is there now. > That would be great, but it would mean the Debian Emacs policy ( https://www.debian.org/doc/packaging-manuals/debian-emacs-policy) and the emacsen-common package, which provides the necessary infrastructure, would need to be upgraded. My understanding is as follows: to build such a Debian package, you'd have to install the byte-compiled files in a directory with the same name as the Emacs package, and add its parent to package-directory-list in site-start.d, is that roughly correct? --001a114451d0717530052c44dc75 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


Stefan= Monnier <monnier@iro.umontr= eal.ca> schrieb am So., 21. Feb. 2016 um 03:19=C2=A0Uhr:
> 1. Not only emacs provides a package mana= ger. Linux distributions also
>=C2=A0 =C2=A0 provide some packages. Not sure if this is a good idea. >=C2=A0 =C2=A0 The same situation is e.g. for python. You can use pip to= install
>=C2=A0 =C2=A0 packages. And there are python packages provided by distr= ibutions.
>=C2=A0 =C2=A0 Some people prefer OS packages, some prefer the native pa= ckage manager.
>=C2=A0 =C2=A0 Not sure what to do about this situation.

It's easy to make a .deb package which installs an Elisp package in the=
way package.el would have installed it (but with global scope).

The two aren't 100% equivalent (upgrading/removing a dpkg-installed
package via package.el won't do the right thing), but the Debian
packages can easily do better than what is there now.

That would be great, but it would mean the= Debian Emacs policy (https://www.debian.org/doc/packaging-manuals/debian= -emacs-policy) and the emacsen-common package, which provides the neces= sary infrastructure, would need to be upgraded.
My understanding = is as follows: to build such a Debian package, you'd have to install th= e byte-compiled files in a directory with the same name as the Emacs packag= e, and add its parent to package-directory-list in site-start.d, is that ro= ughly correct?
--001a114451d0717530052c44dc75--