From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: John Wiegley Newsgroups: gmane.emacs.devel Subject: Re: [ANN] New library stream.el in ELPA Date: Wed, 14 Oct 2015 14:31:13 -0700 Organization: New Artisans LLC Message-ID: References: <87d1whk75h.fsf@petton.fr> <87si5djubt.fsf@petton.fr> <87pp0hjlhj.fsf@petton.fr> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1444858406 17907 80.91.229.3 (14 Oct 2015 21:33:26 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 14 Oct 2015 21:33:26 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Oct 14 23:33:19 2015 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 1ZmTfh-0005vS-4H for ged-emacs-devel@m.gmane.org; Wed, 14 Oct 2015 23:33:17 +0200 Original-Received: from localhost ([::1]:44641 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZmTff-0006Ig-Us for ged-emacs-devel@m.gmane.org; Wed, 14 Oct 2015 17:33:15 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52689) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZmTej-0006Go-DR for emacs-devel@gnu.org; Wed, 14 Oct 2015 17:32:18 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZmTeg-000445-80 for emacs-devel@gnu.org; Wed, 14 Oct 2015 17:32:17 -0400 Original-Received: from mail-pa0-x229.google.com ([2607:f8b0:400e:c03::229]:35142) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZmTeg-000441-2D for emacs-devel@gnu.org; Wed, 14 Oct 2015 17:32:14 -0400 Original-Received: by pacao1 with SMTP id ao1so347449pac.2 for ; Wed, 14 Oct 2015 14:32:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:to:subject:in-reply-to:date:organization:message-id :references:user-agent:mail-followup-to:mime-version:content-type; bh=Ft0dwABkX4lbptxoMWntGu1oNz1h84iG7JfY9Pk8k/c=; b=MilPA+7qMHaP50cfawliSNfvSir2K5FKEFb2nhTlWqxRhKFEKbHAQigPnJUOcsczgW /PZXhVddABnzSSbLsrTZJWWyhA+drGHEXRUctdIlnuSBEnCqRVzz97XYBaZP1pF5d4VC EneeJqfvSY25eb4zt4fIQuZs+1cv1MZXkiEyhhxrQqZPZEU9S46RsxMuF6XoPmqU8Sq4 B9yevQ0n95DvDVih9xTxSyx/aPUgpI3Yw2nff5SiI9MJPBHQJfzPYxzoo1qu8uqhlrtv 5HIX0ns3KYc29vmQ2ye6ee5G/tEG1Muw+E0oKvicCM4j4mobpLIx2BozxoCoKEm6vMhr RJ7Q== X-Received: by 10.66.65.228 with SMTP id a4mr5902377pat.19.1444858333412; Wed, 14 Oct 2015 14:32:13 -0700 (PDT) Original-Received: from Hermes.localdomain (c-67-169-239-227.hsd1.ca.comcast.net. [67.169.239.227]) by smtp.gmail.com with ESMTPSA id ce3sm11381074pbb.35.2015.10.14.14.32.11 for (version=TLS1 cipher=AES128-SHA bits=128/128); Wed, 14 Oct 2015 14:32:12 -0700 (PDT) Original-Received: by Hermes.localdomain (Postfix, from userid 501) id 882F6475C9CD; Wed, 14 Oct 2015 14:32:10 -0700 (PDT) In-Reply-To: <87pp0hjlhj.fsf@petton.fr> (Nicolas Petton's message of "Wed, 14 Oct 2015 21:31:04 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (darwin) Mail-Followup-To: emacs-devel@gnu.org X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400e:c03::229 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:191589 Archived-At: >>>>> Nicolas Petton writes: > What if I extract it in a thunk.el library and install it in master (with > proper tests), and have stream.el use that? (I could also put stream.el in > Emacs, but Stefan thought it would be better to have it in ELPA). Probably I'd prefer to see thunk.el in master, and stream.el in ELPA, since the latter is a bit more special-cased and "implemented in terms of core". If it ends up proving to be a valuable core addition, we can always bring it into master later. We should talk about where to draw "the ELPA divide" at some point too. Core Emacs sort of has at least two separate roles: Functionality the Emacs developers have standardized on -- as a common framework to build packages upon -- and packages that should really be installed anywhere Emacs is installed. John