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 package "Loopy" to Non-GNU Devel? Date: Sun, 25 Feb 2024 20:50:18 +0000 Message-ID: <87edd0z2t1.fsf@posteo.net> References: <871ec398-df6a-44a1-a149-d0014f99b756@protonmail.com> <87wmqz1rr7.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="12137"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Okamsn Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Feb 25 21:51:23 2024 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 1reLT0-0002zC-Ld for ged-emacs-devel@m.gmane-mx.org; Sun, 25 Feb 2024 21:51:22 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1reLSA-0006IH-2v; Sun, 25 Feb 2024 15:50:30 -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 1reLS8-0006I8-72 for emacs-devel@gnu.org; Sun, 25 Feb 2024 15:50:28 -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 1reLS2-0007MC-Rp for emacs-devel@gnu.org; Sun, 25 Feb 2024 15:50:26 -0500 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 04029240029 for ; Sun, 25 Feb 2024 21:50:19 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1708894220; bh=VGRfrsdayUrDXNNDIbSaP4DC+N/SOT77vBpHgt65VhA=; h=From:To:Cc:Subject:OpenPGP:Date:Message-ID:MIME-Version: Content-Type:From; b=dUTZjtPSjC793bxRjCo1pp6EhrE0ZtnPbiFPWnHokUCY82UAqwPllLx8OAkevvpWH YCFaeymv2u0gviKN4Ji5fF/nK6On28D0HlkWLJeGl1uke4YyGWZm9IZLOF2jdiY+MT teLRbvgGl/uTnAGz2cevpxbuedWybxXHTAivve1ldxiOVeTQwDUMd4qfgc/JetaElJ iHtQvsi+YJMAcHXAeBG9woFng1crUKAI0MnLbLY26jT2aagCbcfBL2OcEFwtjbrqd0 /V+iTNDttjWlg/NmG/j8AzhQ16xNL3TFtGBxIWx+rcmTY5uJBYu73YVzMguqg+2dbI XXdbWduSPeDLw== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4TjbVM2crFz6tyY; Sun, 25 Feb 2024 21:50:19 +0100 (CET) In-Reply-To: (okamsn@protonmail.com's message of "Sun, 25 Feb 2024 17:56:16 +0000") OpenPGP: id=7126E1DE2F0CE35C770BED01F2C3CC513DB89F66; url="https://keys.openpgp.org/vks/v1/by-fingerprint/7126E1DE2F0CE35C770BED01F2C3CC513DB89F66"; preference=signencrypt Received-SPF: pass client-ip=185.67.36.65; envelope-from=philipk@posteo.net; helo=mout01.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 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_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:316539 Archived-At: Okamsn writes: > Okamsn wrote: >> Philip Kaludercic wrote: >>> Okamsn writes: >>>> I keep the extension package in the same GitHub repo as the main package for >>>> testing purposes. The Dash functionality was requested by a user, but >>>> Dash is >>>> not used by the rest of the package. Because of that, I put the Dash >>>> functionality in a small separate package. >>> >>> You are talking about the loopy-dash.el file in the same branch, right? >> >> Yes. >> >>> If possible, it would be better if you could at least maintain it in a >>> separate branch. >> >> If I added the file "loopy-dash.el" to an ".elpaignore" file in the main >> branch and used GitHub Actions to push any changes from the main branch >> to another branch containing the file "loopy-dash.el", would that be >> acceptable? Sorry for not answering earlier, this doesn't really solve the issue, since the root issue is that when using package-vc or elpa-admin, you still have two versions of the file in `load-path'. > > Hello, > > I figured out how to make GitHub automatically copy changes of the file > to another branch when the master branch changes, and have listed the > file `loopy-dash.el` in the `.elpaignore` file on the master branch. If we were to disregard examples as those mentioned above, then this would be an acceptable solution, but I'd rather not, unless you categorically reject having two separate and disjoint branches. > I successfully installed the packages locally using the instructions in > the ELPA readme. > > I have attached a patch file. Are there any other changes that you would > like made? I don't think there is anything else (the only thing I can vainly try to bring up is that having a diminutive as the name of a macro is something I find peculiar, and I can imagine would keep a number of other people from using the otherwise nice package, but it seems it is too late for that now?) > Thank you.