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: feature/package+vc 04c4c578c7 3/4: Allow for packages to be installed directly from VCS Date: Tue, 15 Feb 2022 13:34:37 -0500 Message-ID: References: <164484721900.31751.1453162457552427931@vcs2.savannah.gnu.org> <20220214140020.04438C00891@vcs2.savannah.gnu.org> <87bkz9tbcj.fsf@posteo.net> <87o839ypx6.fsf@posteo.net> <87mtisnjcb.fsf@posteo.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="14276"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Philip Kaludercic Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Feb 15 19:54:03 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 1nK2xf-0003PY-HW for ged-emacs-devel@m.gmane-mx.org; Tue, 15 Feb 2022 19:54:03 +0100 Original-Received: from localhost ([::1]:46464 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nK2xd-0006QG-W0 for ged-emacs-devel@m.gmane-mx.org; Tue, 15 Feb 2022 13:54:02 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:56428) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nK2f9-00049z-1h for emacs-devel@gnu.org; Tue, 15 Feb 2022 13:34:55 -0500 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:13500) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nK2f6-0006LY-0j for emacs-devel@gnu.org; Tue, 15 Feb 2022 13:34:54 -0500 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 8F0F7805E4; Tue, 15 Feb 2022 13:34:49 -0500 (EST) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id E1373805B4; Tue, 15 Feb 2022 13:34:47 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1644950087; bh=rj3tH6RRl9E0Q/Lu4ki2zoYsrb5bRoTp2wKOkwIcOOg=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=RsBWBqWXPy932gn8Y21M3UuYovRqxjrZwT3xfQRl3IXMTQ4Db0YIayvC8fggnEvO6 KHIHAvQ8K3IoN4pfPygJraq4b4gytcIlppvAYjE0fHD4WLp+/9RwRein3Hb74PSK7g ELrmfDrkMHaR/+vSGwuETASWeKia1BgdCq94qUrXPxN9n7kqqIr5kUDwc9K622HwYn Oc+jXQvXCLwGxPzUjTr5Ju9HchrSfJP4LFhe2jzxAENkYN3T2Lpt9WEJSYaaFgjbXO LbWSV/jZoaVr2Cs8kDVSm+3sUor8CIqrDrvaxLMqJ9/cxJHvNhSPHjHESztjTR+15h Hu/5jRRK5Uybg== Original-Received: from pastel (unknown [45.72.237.157]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id B65E9120920; Tue, 15 Feb 2022 13:34:47 -0500 (EST) In-Reply-To: <87mtisnjcb.fsf@posteo.net> (Philip Kaludercic's message of "Tue, 15 Feb 2022 17:13:56 +0000") 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, T_SCC_BODY_TEXT_LINE=-0.01 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" Xref: news.gmane.io gmane.emacs.devel:286343 Archived-At: Philip Kaludercic [2022-02-15 17:13:56] wrote: > Stefan Monnier writes: >>> The -devel doesn't necessarily indicate that directly, I just meant it >>> was worth somehow explicitly indicating that this is a VCS-package. >> But what I'm saying is: why not put no "-*" at all, since that's what >> `package.el` has been using so far for those cases (tho these had to be >> "installed" by hand)? > I get that, my question still remains. Or to rephrase it, what is the > advantage of displaying package names with the same names as the > directories they are found in? Not sure what "display" has to do with it. The name of the package is beyond our control. So the choice is not what to display but what name to give to the directory. `` is a name that already works. `-devel` is a name that currently doesn't work. In any case, this is not an important issue, I think (at least, as long as "devel" is not a valid version name). >>>> IIUC for those VCS-installed packages we generate the -pkg.el file >>>> ourselves, so it should be fairly easy to make sure that file provides >>>> the needed info so we don't need to guess. >>> >>> Yes, but again, if I just clone a project into elpa/devel, this won't >>> work. It could be argued that this shouldn't be supported because it is >>> a different issue, and the elpa/... directories maintained by >>> package.el, but in that case I would like some other way to have >>> package.el manage non-versioned local source. >> >> I'm sorry, I don't understand what you're saying here. Who&how does >> "just clone a project into elpa/devel" and what do you mean by "elpa/devel"? > > What I meant was that all directories in ~/.emacs.d/elpa/devel could be > automatically detected and loaded. That's already the case if `~/.emacs.d/elpa/devel` is in `package-directory-list`, so I don't understand how that relates to what we're discussing. > One case where this could be useful for anyone using submodules in > a versioned configuration. Again, I don't understand the relationship. Maybe if you could give a concrete example scenario? >> BTW, I think we should choose some `package--` prefix for the >> vars&functions related to this new "install from VCS" functionality. > If it is possible to extract the relevant functionality form package.el > to package-.el, then of course, but I can also try to stick to this > otherwise. Do you think this should also include renaming package-fetch? Yes. Depending on how good "--" is, we may want to add shorter aliases, of course, but I think that using a `package--` prefix will help clarify the design. Stefan