From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Stephen Eilert" Newsgroups: gmane.emacs.devel Subject: Re: Emacs Package Management Date: Fri, 1 Aug 2008 22:58:21 -0300 Message-ID: <485b0c380808011858h4ef97984qb4d2e52ec95ce07f@mail.gmail.com> References: <485b0c380808011427n4d3144eey3f8daf3abac83bf4@mail.gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_9125_10711771.1217642301360" X-Trace: ger.gmane.org 1217642329 19376 80.91.229.12 (2 Aug 2008 01:58:49 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 2 Aug 2008 01:58:49 +0000 (UTC) To: emacs-devel@gnu.org, tromey@redhat.com Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Aug 02 03:59:39 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1KP6PA-0007rs-4c for ged-emacs-devel@m.gmane.org; Sat, 02 Aug 2008 03:59:37 +0200 Original-Received: from localhost ([127.0.0.1]:35246 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KP6OE-0000N0-3F for ged-emacs-devel@m.gmane.org; Fri, 01 Aug 2008 21:58:38 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KP6O4-0000K3-32 for emacs-devel@gnu.org; Fri, 01 Aug 2008 21:58:28 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KP6O2-0000J4-63 for emacs-devel@gnu.org; Fri, 01 Aug 2008 21:58:27 -0400 Original-Received: from [199.232.76.173] (port=39440 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KP6O1-0000Ix-UB for emacs-devel@gnu.org; Fri, 01 Aug 2008 21:58:26 -0400 Original-Received: from rv-out-0708.google.com ([209.85.198.246]:49576) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KP6O0-0003Xk-No for emacs-devel@gnu.org; Fri, 01 Aug 2008 21:58:25 -0400 Original-Received: by rv-out-0708.google.com with SMTP id k29so1365869rvb.6 for ; Fri, 01 Aug 2008 18:58:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=DiBpCT2XDswUaRdvZqZxJfpK/Df1DEHY/LuvK9OL6+g=; b=X4BpQjNSI0MUqQMggEO6Cj7gLx/ZQWwURK9BAjEN6aM+ODgYH/aNw5wTSMxKgcmSLr mqyklZvFhX34N+zrHGOwflZBlwSGqRBLiEDjqwrQcLFuTNuVeKLQxr/27EqdZCVx6WR/ /bNuaM8VHiR2E+NIBXOpXet/clATh/VcPeQGI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=SfccNDXgNMcQ2NTL6+D5Gapl/dF8Zb2j4K175w5Kg4cWX4P9EsAAU2dQV/6sr/Lq89 oXHHjhxfjocfHl+X+tk8CJV251nq3MbsYaLfwmx0a+yemPshZ/YFfMVk7a606w5Z0nKM nGD4qEDZSHtXmKMR2Yv59ZYj8c4442KOOLz18= Original-Received: by 10.141.171.6 with SMTP id y6mr6296587rvo.84.1217642301352; Fri, 01 Aug 2008 18:58:21 -0700 (PDT) Original-Received: by 10.141.115.15 with HTTP; Fri, 1 Aug 2008 18:58:21 -0700 (PDT) In-Reply-To: X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:101933 Archived-At: ------=_Part_9125_10711771.1217642301360 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Fri, Aug 1, 2008 at 7:58 PM, Tom Tromey wrote: > >>>>> "Stephen" == Stephen Eilert writes: > > Stephen> With a slightly improved system, we could have > Stephen> dependencies. This could make easier to solve the > Stephen> aforementioned problem of gathering multiple, independent > Stephen> packages from different sources. > > Just FYI -- package.el (the elisp side of ELPA) does handle dependencies. > > :-) It appears I have overlooked that. Nice to know. > > > Stephen> Does anyone see a major flaw in a system like that? Or is it > Stephen> a matter of "show me the code and I'll comment"? ELPA could > Stephen> be the starting point. > > There was a discussion a while ago on this list. RMS wanted to > restrict the available packages to those which had been assigned to > the FSF, but I did not agree with that. Meh. Just set up a repository maintained by the FSF by default and leave the ability to add others, at the user's discretion. It won't prevent anything that isn't already being done, as it is just for convenience. > > > I would reconsider my position if the Emacs maintainers were > interested -- I think it would be useful to Emacs users if there were > a simple, standard way to install and activate packages. Definitely. Grouping modules together (instead of all over the web at some guy's personal homepage) would be just an added bonus. > > > However, this would still not help you directly, because I think some > of the packages you want are not assigned. So, you would have to > solve that problem as well. One problem at a time ;) --Stephen programmer, n: A red eyed, mumbling mammal capable of conversing with inanimate monsters. ------=_Part_9125_10711771.1217642301360 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline

On Fri, Aug 1, 2008 at 7:58 PM, Tom Tromey <tromey@redhat.com> wrote:
>>>>> "Stephen" == Stephen Eilert <spedrosa@gmail.com> writes:

Stephen> With a slightly improved system, we could have
Stephen> dependencies. This could make easier to solve the
Stephen> aforementioned problem of gathering multiple, independent
Stephen> packages from different sources.

Just FYI -- package.el (the elisp side of ELPA) does handle dependencies.

:-)
 
It appears I have overlooked that. Nice to know. 


Stephen> Does anyone see a major flaw in a system like that? Or is it
Stephen> a matter of "show me the code and I'll comment"? ELPA could
Stephen> be the starting point.

There was a discussion a while ago on this list.  RMS wanted to
restrict the available packages to those which had been assigned to
the FSF, but I did not agree with that.
 
Meh. Just set up a repository maintained by the FSF by default and leave the ability to add others, at the user's discretion. It won't prevent anything that isn't already being done, as it is just for convenience. 


I would reconsider my position if the Emacs maintainers were
interested -- I think it would be useful to Emacs users if there were
a simple, standard way to install and activate packages.
 
Definitely. Grouping modules together (instead of all over the web at some guy's personal homepage) would be just an added bonus.
 


However, this would still not help you directly, because I think some
of the packages you want are not assigned.  So, you would have to
solve that problem as well.
 
One problem at a time ;)
 

--Stephen

programmer, n:
A red eyed, mumbling mammal capable of conversing with inanimate monsters.

------=_Part_9125_10711771.1217642301360--