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: Thu, 14 Mar 2024 18:52:18 +0000 Message-ID: <87o7bgsl25.fsf@posteo.net> References: <871ec398-df6a-44a1-a149-d0014f99b756@protonmail.com> <87wmqz1rr7.fsf@posteo.net> <87edd0z2t1.fsf@posteo.net> <77affe05-eab3-42c3-beab-f8f2d29e12dd@protonmail.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="27598"; 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 Thu Mar 14 19:53:21 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 1rkqCe-0006vx-HA for ged-emacs-devel@m.gmane-mx.org; Thu, 14 Mar 2024 19:53:20 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rkqBn-0006JW-9w; Thu, 14 Mar 2024 14:52:27 -0400 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 1rkqBm-0006JN-KY for emacs-devel@gnu.org; Thu, 14 Mar 2024 14:52:26 -0400 Original-Received: from mout02.posteo.de ([185.67.36.66]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rkqBj-0007kT-P7 for emacs-devel@gnu.org; Thu, 14 Mar 2024 14:52:26 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 0375F240101 for ; Thu, 14 Mar 2024 19:52:19 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1710442340; bh=ZciaC73oTN5ZXLrj1udZyHDVMB8X+/NMuIUAvS284JU=; h=From:To:Cc:Subject:OpenPGP:Date:Message-ID:MIME-Version: Content-Type:From; b=Vd9kpNc7ZV6PTrkTwKhnClQG+hO1CyRALEDR6xpdXgBxm4EHrZLmETLiJk/zhIapB fwwM6WZbh5dEEZb93o2iaXTfbOgeplAcDgp63PTZgSFpLSQ0KcxK+UaBfTze52JDsH w0i7EFNHC5FmXn2jpV3/ztdhc0AOQVn5INnuHSw1UUoiBtjTpiTpTJG+2YemX5QFDv 5/V/xNeyQRdDu2BGFUgHlNsayd4HYSe8xg6u2V+P9tpge9R3hQmjy74Cjqs8imxVwy TkWhui4a18kXzlXGeWAFGfZx6NVfWiKklcj3jhDCc2uw7tSQqMFTsD3pe4N4DdPduE oIEKo75n+LZMA== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4Twc1v3G2Mz6twS; Thu, 14 Mar 2024 19:52:19 +0100 (CET) In-Reply-To: <77affe05-eab3-42c3-beab-f8f2d29e12dd@protonmail.com> (okamsn@protonmail.com's message of "Wed, 28 Feb 2024 01:34:46 +0000") OpenPGP: id=7126E1DE2F0CE35C770BED01F2C3CC513DB89F66; url="https://keys.openpgp.org/vks/v1/by-fingerprint/7126E1DE2F0CE35C770BED01F2C3CC513DB89F66"; preference=signencrypt Received-SPF: pass client-ip=185.67.36.66; envelope-from=philipk@posteo.net; helo=mout02.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_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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:317052 Archived-At: (Sorry for the late response) Okamsn writes: > Philip Kaludercic wrote: >> 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 would like to keep the development of the packages together, since I > still change the implementation details. Having them together makes > testing for breakage much easier. One last idea would be to use worktrees, i.e. basically keep development in separate branches that are simultaneously checked. > What if I also had GitHub copy changes into a separate branch that only > contained the Loopy package and the documentation files? This would > avoid having the two copies of `loopy-dash.el`. Would that work for > Package VC? No, since upon installing loopy as a VC package, you'll still have the loopy-dash.el file as part of the checked out repository and the loopy-dash.el provided by the dependency. >>> 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?) > > I think that it is too late, because it has existed on MELPA for a few > years with that name. If it helps, I was not thinking of it as a > diminutive, just the normal adjective and the slang usage: > https://www.thefreedictionary.com/loopy. I acknowledge that your point > probably also applies for the slang definition, but I still like the name. In that case forget my comment. -- Philip Kaludercic on peregrine