From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: decision on moving core packages to ELPA; also move to obsolete? Date: Wed, 16 Dec 2020 13:35:01 -0500 Message-ID: References: <86a6ugnopl.fsf@stephe-leake.org> <83im94b17m.fsf@gnu.org> <834kknatxs.fsf@gnu.org> <83sg86apqb.fsf@gnu.org> <865z52oqfp.fsf@stephe-leake.org> <86wnxinbnx.fsf@stephe-leake.org> <83o8iuann7.fsf@gnu.org> <83h7omakyw.fsf@gnu.org> <83pn398wol.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="38560"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: daniele@grinta.net, stephen_leake@stephe-leake.org, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Dec 16 19:36:25 2020 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 1kpbey-0009ub-K2 for ged-emacs-devel@m.gmane-mx.org; Wed, 16 Dec 2020 19:36:24 +0100 Original-Received: from localhost ([::1]:38318 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kpbex-0004OE-Gr for ged-emacs-devel@m.gmane-mx.org; Wed, 16 Dec 2020 13:36:23 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36886) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kpbdk-0002ac-UO for emacs-devel@gnu.org; Wed, 16 Dec 2020 13:35:09 -0500 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:37040) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kpbdj-0001ue-02; Wed, 16 Dec 2020 13:35:08 -0500 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id A7A02100246; Wed, 16 Dec 2020 13:35:05 -0500 (EST) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 001FF100225; Wed, 16 Dec 2020 13:35:03 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1608143704; bh=MeTEVDmjaNrmbnUX8n2R2u5z+zyx9gZZzBMCdKEISAE=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=gqv8vIX8rBPYocjVGZV/LAMaZKopQllCVuBoB6W8/9WmfZXUG5gmiliIsEdEXYjDU k7GaJSt3WZs9SlmAPI4F+silBRNmhUhC30X3Jxg/VbPqSuWK20YN1zDz7Fjxs344xC kDGfs+kigzN/IgDiJhsoguX9zou3DAjwSV65VpmjfDGjlYkvyvp0YRyYUBLGPJ0lBc HhmaCbBecpbtckKaTvazs0ATeRSTTqxgX49RmzamkvY1Kks/WiOm+9yVCV/P8wpbvM zlv1tD/TrQjQnN6Ktd+UlWQlYKkyMsYUKU2jf8+1BFUbAKZjVjnSCpdH+rHYMVmaZn gDiHC+0iQ0SNg== Original-Received: from alfajor (69-165-136-52.dsl.teksavvy.com [69.165.136.52]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id B0A901204AE; Wed, 16 Dec 2020 13:35:03 -0500 (EST) In-Reply-To: <83pn398wol.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 16 Dec 2020 19:53:14 +0200") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, 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.23 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" Xref: news.gmane.io gmane.emacs.devel:261025 Archived-At: > Here's what I think we should have working to start bundling ELPA > packages: Then I think the "git submodule" approach proposed earlier by Andrea is the better solution: every ELPA package we want to include will have a branch in `emacs.git` (e.g. with name `elpa/[PKGNAME]`) and in Emacs's `master` branch we will add git submodules which refer to (specific revisions on) those branches. This way a Git checkout can also contain those ELPA packages. We can easily control which version of a package is included into any given version of Emacs because git submodules refer to specific revisions. And those `elpa/[PKGNAME]` branches can easily kept in sync with the corresponding branches in `elpa.git` (and upstream if applicable). > 3. Users > > We need a clear picture of how this Emacs will be installed and > used, both when installed from a distro and when built locally > from the source tarball. Maybe there's nothing to discuss here, > but I at least don't yet have such a clear picture. It should be > possible to install, upgrade, and downgrade such packages, as much > as possible using the same package.el commands as for unbundled > packages. As a minimum, AFAIU we will need to provide a directory > in the tarball/installation that will have the same role as > ~/.emacs.d/elpa/, because a tarball cannot possibly install files > in the users' home directories. We will place the submodules under some `elpa` subdirectory of our choice after which we simply have to add that directory to the default value of `package-directory-list`. Stefan