From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Adding use-package to core Date: Sun, 13 Nov 2022 09:31:11 +0200 Message-ID: <83y1sfl39c.fsf@gnu.org> References: <87lep4jeeb.fsf@gmail.com> <87o7to2dfy.fsf@gmail.com> <87y1ssugaf.fsf@posteo.net> <875yfw6kbx.fsf@gmail.com> <87r0ykufh8.fsf@posteo.net> <87sfiyl6nb.fsf@posteo.net> <87pme1ddsn.fsf@gmail.com> <871qqhby2k.fsf@posteo.net> <87leopdbsw.fsf@gmail.com> <87tu3dagj5.fsf@posteo.net> <87eduhd7m7.fsf@gmail.com> <87iljk1voy.fsf@posteo.net> <874jv4z2th.fsf@posteo.net> <87mt8wxjjf.fsf@posteo.net> <877d009n8a.fsf@gmail.com> <87o7tbwcvw.fsf@posteo.net> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="2370"; mail-complaints-to="usenet@ciao.gmane.io" Cc: stefankangas@gmail.com, johnw@gnu.org, relekarpayas@gmail.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Philip Kaludercic Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Nov 13 08:31:33 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ou7Sn-0000VK-Gh for ged-emacs-devel@m.gmane-mx.org; Sun, 13 Nov 2022 08:31:33 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ou7SM-0000fv-NY; Sun, 13 Nov 2022 02:31:06 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ou7SK-0000fh-RA for emacs-devel@gnu.org; Sun, 13 Nov 2022 02:31:04 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ou7SK-0004Zb-32; Sun, 13 Nov 2022 02:31:04 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=nzwtOU9HdixgCuXanfIJQnlz8pWoILPgu5OrTSMBWLs=; b=UfFi7GGE4mhj JVevgn2ncv1gV/mParJGjJJZHEhFyHo/GkTIfsC6Guxps3iupzooMsI5bv9Ilx4L7VGHrP5/tLgjT ciwsrgvUNlhpuwA7mklk1/Xn32AiPRcdzL8uyIVPPWQvD4HNqz8xKtz96HCjHQYL2daE29IBrIOIT yvbBsCExtIRcq1LkasfuxpA80bmcnCJm8RhdSq6s4+6G1b/equZcUwZgdFJIihyAF2fk67tmjtuB9 Isu1pHbLHj6YoVsx/e0EJj8XgLBuLoK1WAXrtxpou4fVuvq16chK9xHyDk2XKpzzD2yZLlkpwo/jN XXEu9dQIbL1c6S+pK/X6OA==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ou7SJ-0006io-HI; Sun, 13 Nov 2022 02:31:03 -0500 In-Reply-To: <87o7tbwcvw.fsf@posteo.net> (message from Philip Kaludercic on Sun, 13 Nov 2022 07:07:47 +0000) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:299710 Archived-At: > From: Philip Kaludercic > Cc: John Wiegley , Payas Relekar , > Stefan Monnier , emacs-devel > > Date: Sun, 13 Nov 2022 07:07:47 +0000 > > Stefan Kangas writes: > > >> I'm entirely in support of the code and its development moving directly into > >> core. Whichever best supports the Emacs developers and the needs of the > >> community, since it is more than likely that future work will be carried out > >> by others. I'm ready to hand it off in whatever way is desired by the team > >> here. > > > > IMHO, for that to make sense, someone capable would have to volunteer to > > maintain it on our side. If we don't have such a volunteer, it makes > > more sense to me to keep development external for now. > > > > If we see a need to move development fully into core in the future, we > > can always do that, but the reverse is harder. > > I agree, a transitory stage where use-package is still maintained > externally sounds like the safer bet for now. I don't share Stefan's fears. If the only issue with moving use-package to core is that someone must step forward to take the responsibility for maintaining it, I think we can move it into core without fear. I see no reason for making a dedicated maintainer for use-package a prerequisite for importing it, given what John says about its stability. It's a non-issue.