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 22:08:33 +0200 Message-ID: <83v8nik472.fsf@gnu.org> References: <838rkels13.fsf@gnu.org-NGltIw7----9> <83zgcuk8pb.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="6001"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: xenodasein@tutanota.de Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Nov 13 21:08:50 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 1ouJHc-0001J4-B6 for ged-emacs-devel@m.gmane-mx.org; Sun, 13 Nov 2022 21:08:48 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ouJHI-00086I-GU; Sun, 13 Nov 2022 15:08:28 -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 1ouJHG-00085i-Ce for emacs-devel@gnu.org; Sun, 13 Nov 2022 15:08:26 -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 1ouJHG-0005VO-2C; Sun, 13 Nov 2022 15:08:26 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=AU2noccrrnJ/mijExhWPEnFLP/ESpEJHfvuveTwxdLk=; b=jfLWE+E/VLI7bUESdQMY jtG5oTAV/QJyHedGkkL5QjibSU0N/rucN7dtZ51L/yxzK/3eNMNfKxf+L8aqnlFpCPO6n2ZGoLybW emJbw5x8khk1ko9OzETmUiIXuKzQd+0Npd7gaeXGBgblZKaYQXEkoDbF4Sa51GxnbBOgEEGOtftE+ S1El44oOwlGb8PunyRSKcN+IH0RKmQmXqSOCNa3vBGTFND6OSoW8+hsLVNsAaxq0Zj7hD27//fMXG PckGfA8ymYFovfPVkW3B6d2LhwPHojCFVY8a0H0mgInmpQR7gxqp6FsOUMwFUVMKh4spgnU/jjb6L yC3Z7kzIvxZ6Kw==; 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 1ouJHE-0004mZ-LJ; Sun, 13 Nov 2022 15:08:25 -0500 In-Reply-To: (xenodasein@tutanota.de) 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:299753 Archived-At: > Date: Sun, 13 Nov 2022 20:19:00 +0100 (CET) > From: xenodasein@tutanota.de > Cc: emacs-devel@gnu.org > > > The packages in lisp/ aren't orphans, just look at the Git logs. (How > > can you seriously consider the Lisp packages in core "frozen" when we > > average 5000 commits a year for the past ten years?? Where do all > > those commits go, in your opinion?) > > > > There seems to be many like allout that don't receive a commit for > decades (apart from a typo fix or two). Which means they are probably not used by many, or don't need any changes. That's natural. > AFAICT most go to new additions. Not true. > Stefan K seems to do a lot of thankless housekeeping in that direction, I guess you only looked at the last year or two. > but more importantly there was the force of nature from Lars before you > ahem frustrated him away, so my criticism mostly applies to from then on; > by all means if we can get Lars back to fixing the million line > interdependent Elisp code, I'll grunt no more.  The way I see it options > are immediately to stop anything else and to hold communions and pray to > get him back, or just start downsizing. Once again, I'm talking about the last decade, not the last couple of years. You are missing the big picture. And anyway, I don't see what all this has to do with having a package in core or not.