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: [NonGNU ELPA] New packages: Vcomplete, swsw Date: Sun, 22 May 2022 12:29:06 -0400 Message-ID: References: <875ylx4yvn.fsf@dsemy.com> <87h75hyehx.fsf@posteo.net> <87sfp15zp1.fsf@dsemy.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="24284"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: Philip Kaludercic , emacs-devel@gnu.org To: Daniel Semyonov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun May 22 18:30:52 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 1nsoTj-00069v-Ov for ged-emacs-devel@m.gmane-mx.org; Sun, 22 May 2022 18:30:51 +0200 Original-Received: from localhost ([::1]:38250 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nsoTi-0005Fc-Ny for ged-emacs-devel@m.gmane-mx.org; Sun, 22 May 2022 12:30:50 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:55824) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nsoS9-0004YA-LG for emacs-devel@gnu.org; Sun, 22 May 2022 12:29:13 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:27352) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nsoS7-0004jY-9z for emacs-devel@gnu.org; Sun, 22 May 2022 12:29:12 -0400 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 8193F442277; Sun, 22 May 2022 12:29:09 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id D7811442255; Sun, 22 May 2022 12:29:07 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1653236947; bh=m6h5dPfGkG/PRLd0hTSrrQx3rhx0gAADXFBrF2oqgBQ=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=m0W+2wzFD2jBzHSa5RYfTW402xU4VzOJd1GkqSpSRzG1PDMobEbwLP2wO2L2L08hn ecC+CZHZjevdBmiBVBZ86Cq6K1H5m8wfVKpNBbTsgev8ffoGE+p9FfYb3oL6wCeTYV StsqzDkzfzc3x4tNKeupnrEIU+EZ6DrWPfbRxH+p/bH0DoA8eQ/OgqVeMPTbMx/GIx 8aZ3G/tCtCUeAJbitlZ7/20kJlJFEp4TSENglYVVOPffTvRaEfUjzIPvPS0gnHCkWL NVaIr9G4uKDdQf8I2C2XzT3JsRZfnvyE2B92HX+Q16sEueotIeXL+cuuuLdNGXBfSd gqqY8MaY6ppbg== Original-Received: from pastel (unknown [45.72.221.51]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id AA8ED1200D3; Sun, 22 May 2022 12:29:07 -0400 (EDT) In-Reply-To: <87sfp15zp1.fsf@dsemy.com> (Daniel Semyonov's message of "Sun, 22 May 2022 18:55:54 +0300") 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:290100 Archived-At: > Semi-intentional... now that you mention it, is it possible for two > (related) packages to share the same git repository? Kind of, when really necessary, but with various caveats. I think you'd be better off with a single package that just happens to collaborate with Embark when Embark is used (i.e. without an explicit dependency on Embark, which also means it should not require Embark to compile vcomplete-embark), or else to move it to a separate repository. > Since both packages are complex (as in, they contain multiple files), > when I generate my own package tar (for distribution on my site for > example, as the packages weren't available on any archive before), it > needs to contain a -pkg.el file for Emacs to install it (or at > least that's what I remember from testing I did long ago). Yes, but that doesn't mean it should be in the Git. > I will admit this file should just be generated automatically during the > build process in this case too, I just never got around to implementing > that. You don't need to. The elpa.gnu.org scripts do that for you (and they even sometimes trip over themselves when there's a competing -pkg.el in the Git). > BTW, when the packages are first imported, would the latest commit be > used, No: we ask Git when's the last commit that touched `Version:`. Stefan