From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Philip Kaludercic Newsgroups: gmane.emacs.devel Subject: Re: Adding use-package to core Date: Sun, 13 Nov 2022 07:07:47 +0000 Message-ID: <87o7tbwcvw.fsf@posteo.net> 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> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="19524"; mail-complaints-to="usenet@ciao.gmane.io" Cc: John Wiegley , Payas Relekar , Stefan Monnier , emacs-devel To: Stefan Kangas Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Nov 13 08:08:15 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 1ou76E-0004sq-IX for ged-emacs-devel@m.gmane-mx.org; Sun, 13 Nov 2022 08:08:14 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ou75v-0006lF-16; Sun, 13 Nov 2022 02:07:55 -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 1ou75t-0006kn-BV for emacs-devel@gnu.org; Sun, 13 Nov 2022 02:07:53 -0500 Original-Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ou75r-0000Lc-D8 for emacs-devel@gnu.org; Sun, 13 Nov 2022 02:07:53 -0500 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id BA39E240026 for ; Sun, 13 Nov 2022 08:07:49 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1668323269; bh=rJfZNFUR4HKUCMIGxshBeVaxmzXFEoQUqHuMO2XX6wg=; h=From:To:Cc:Subject:Date:From; b=IRNOenqvoTJY52d20gzVnR2jc5r3CFtcGac+7Rm5GDsaSqBrecqTz0SKPUsnR4maq H+e+wtvbVsE7sPj2yVAMTr+M0745H5tzzwdR2Az2pwCnDUKw89UjCXed4JlGtgjVsy 0OOi7QhP/yLjyZyaNrXvJVXAMc+UckLAaR7QtimlGt3ou6kPajVGOxOTQoumlkLBv9 /Wu1XGc+l53eq67IboKGFHvzoSrTJ7a/wHBg77lCDuEeu1awkNpV9whTlkWsG/MkWY nFSeKmxcq1YVXF9MKJw6SNZY7dE/oWL07Jmfj1pawxa8I6xjlIbRfJ+6HvMwfs/k5e z5Bac2ONH/DkA== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4N93Rm6lxfz9rxG; Sun, 13 Nov 2022 08:07:47 +0100 (CET) In-Reply-To: (Stefan Kangas's message of "Sat, 12 Nov 2022 21:25:37 -0800") Received-SPF: pass client-ip=185.67.36.65; envelope-from=philipk@posteo.net; helo=mout01.posteo.de X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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:299706 Archived-At: Stefan Kangas writes: > John Wiegley writes: > >>>>>>> Payas Relekar writes: >> >>> I would personally like to see the package in core if at all possible, and >>> John has also expressed interest in that. Personally I'd prefer if >>> development continues in core after upstreaming, but it is upto John to >>> decide. I know that Modus-themes and Org both are developed out of tree, and >>> only merged in when the package version is bumped. Which means history is >>> lost, but clearly that hasn't been a problem and maintainers of those >>> packages prefer it. >> >> 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. > (If we want to preserve history when making such a move at a later date, > we could just delete our existing copy of the file from emacs.git and > then merge the full git history, just as we did with eglot.el.) In that case, what is left is completing the .texi manual, or am I mistaken? After that, I suppose that placing the right files in the right places in emacs.git will be less that a days work.