From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Jambunathan K Newsgroups: gmane.emacs.devel Subject: Re: Packages + elpa.gnu.org Date: Thu, 28 Oct 2010 13:25:34 +0530 Message-ID: <81ocaesqdl.fsf@gmail.com> References: <81eic0wsre.fsf@gmail.com> <87y6a86muv.fsf@stupidchicken.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1288252575 938 80.91.229.12 (28 Oct 2010 07:56:15 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 28 Oct 2010 07:56:15 +0000 (UTC) Cc: emacs-devel@gnu.org To: Chong Yidong Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Oct 28 09:56:13 2010 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.69) (envelope-from ) id 1PBNLJ-0007M5-3t for ged-emacs-devel@m.gmane.org; Thu, 28 Oct 2010 09:56:13 +0200 Original-Received: from localhost ([127.0.0.1]:36823 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PBNLI-0004K5-1g for ged-emacs-devel@m.gmane.org; Thu, 28 Oct 2010 03:56:12 -0400 Original-Received: from [140.186.70.92] (port=53056 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PBNL8-0004I3-CS for emacs-devel@gnu.org; Thu, 28 Oct 2010 03:56:03 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PBNL2-0002MC-CH for emacs-devel@gnu.org; Thu, 28 Oct 2010 03:56:02 -0400 Original-Received: from mail-yw0-f41.google.com ([209.85.213.41]:55357) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PBNL2-0002M2-9S for emacs-devel@gnu.org; Thu, 28 Oct 2010 03:55:56 -0400 Original-Received: by ywl5 with SMTP id 5so538381ywl.0 for ; Thu, 28 Oct 2010 00:55:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:subject:references :date:in-reply-to:message-id:user-agent:mime-version:content-type; bh=85X/IzUKGqaN3bCaTtzr/XyEKZyYI+FEy3mBll+4zs0=; b=ju0zXyOEps7ff91JJmE+8A38Sv7tCMQL4OOM0OFQk3+2hsYjSrU5pNG6Ik0JW10ABk vxsLg5+dAAKe20yzaM0ju2YXND5MZA/hRyLxHj189zj6gjF3CBYL8UfpxBHorgi0bWDk jsoV3faWTRixDu2llvGXvpiB7jstgDj5+FSmk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type; b=s4XfWF5tKZ18x9MT2jwgAeV+FceCMt9Kf06SK+boiuUnlvCMF3Orr4vr8CyMpS0aVm J3ksTxtmfCD3OeaiG/GF0h6/79LW4/PtQmfUT1BVXXoDeTKbnFVnPu5arRNNqTcSr7qt xTS4d+SLZCGmn2qmJWdipHuDLtZLCMaEVj/qk= Original-Received: by 10.150.230.10 with SMTP id c10mr19324734ybh.3.1288252555637; Thu, 28 Oct 2010 00:55:55 -0700 (PDT) Original-Received: from JAMBU-NETBOOK ([115.242.254.206]) by mx.google.com with ESMTPS id t9sm602091ybe.9.2010.10.28.00.55.52 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 28 Oct 2010 00:55:54 -0700 (PDT) In-Reply-To: <87y6a86muv.fsf@stupidchicken.com> (Chong Yidong's message of "Fri, 08 Oct 2010 23:55:52 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.91 (windows-nt) X-detected-operating-system: by eggs.gnu.org: GNU/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:132158 Archived-At: Hello Chong Chong Yidong writes: >> 3. Does the package manager expect that builtin packages be versioned in >> a special way. For example, can the stable release be called 7.0.1 >> while a daily snapshot be called 20101008? > > The package manager uses the most recent version of a package, as > defined by `version-list-<'. > For a builtin package which is actually a bunch of files how and wherefrom the package manager picks up the name and version number. I am specifically interested in Orgmode. >> 4. Any general guidelines on what packages would be accepted there and >> how often an update can happen. Are daily snapshots allowed. > > The main requirement is for package copyrights to be FSF assigned. I > think providing dailies is fine. Since dailies are permitted, I believe it would be a good idea to recognize - if not by specification atleast by convention - multiple streams of releases. For the sake of discussion, orgmode one can have these two packages simultaneously in the repo. org/stable-x.y.z.tar and org/unstable-x.y.z.tar Here stable and unstable are the two 'streams' for the package and '/' is the separator. I see the following advantages: 1. From the user side, there is no confusion on what he is setting-up himself against. 2. From the maintainer's side, the two packages could be versioned separately. For example, the stable package could use a 7.x scheme and the unstable package could do a '20101028' versioning scheme. More importantly, M-x package-upload-file wouldn't knock off stable entry in archive-contents favoring a daily release which has a higher version number. One important side-effect of granting 'streams' an official stauts would be that that sorting by name would sort really by name component of the package as the primary key and 'stream' component as a secondary key. This is very necessary as there would be no way a random package can intersperse between org/stable and org/unstable by mere choice of name. Speaking of package manager being intelligent, when I do M-x list-packages I am inclined to think the list is sorted in the following order - - with package status being the primary key. The problem is I get 3 entries for orgmode - available, installed, obsolete - that are far separated from each other. Any ways I can filter and sort these entries? Can this be captured in the documentation. I welcome any ideas or suggestions. Jambunathan K.