From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtpout2.vodafonemail.de (smtpout2.vodafonemail.de [145.253.239.133]) by sourceware.org (Postfix) with ESMTPS id 37848385AC22 for ; Tue, 5 Oct 2021 18:24:51 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 37848385AC22 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=nexgo.de Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=nexgo.de Received: from smtp.vodafone.de (smtpa08.fra-mediabeam.com [10.2.0.39]) by smtpout2.vodafonemail.de (Postfix) with ESMTP id 4420061EBF for ; Tue, 5 Oct 2021 20:24:50 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nexgo.de; s=vfde-smtpout-mb-15sep; t=1633458290; bh=m+ow4GtOaQeqQpIbwzVBW/oDg7hGVLtFN2H+1/hN9Ks=; h=From:To:Subject:References:Date:In-Reply-To; b=EY2lnpBpngVqk6Lr7jvudKGMfo9t+xi8y2LiSp026QhdR7f0CNo7DKSaYdVWRZPzX TIRoeCiVWjjoCjU3MpH2HPn67l6MAnj9t8f04Ik0UWSempgs6iGwZw3gR3kL4kDuUF lL95f9raDF3CfPD+EzdgJxdSmud91UM67DvqAKxQ= Received: from Gertrud (p54a0cb96.dip0.t-ipconnect.de [84.160.203.150]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by smtp.vodafone.de (Postfix) with ESMTPSA id A6225140586 for ; Tue, 5 Oct 2021 18:24:45 +0000 (UTC) From: Achim Gratz To: cygwin-apps@cygwin.com Subject: Re: Question about 'provides' and emacs packaging References: Date: Tue, 05 Oct 2021 20:24:44 +0200 In-Reply-To: (Ken Brown via Cygwin-apps's message of "Tue, 5 Oct 2021 11:51:47 -0400") Message-ID: <871r4zba8j.fsf@Rainer.invalid> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-purgate-type: clean X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de X-purgate: This mail is considered clean (visit http://www.eleven.de for further information) X-purgate: clean X-purgate-size: 2066 X-purgate-ID: 155817::1633458285-00007455-B1FE3ED5/0/0 X-Spam-Status: No, score=-3030.4 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_BARRACUDACENTRAL, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin-apps@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Cygwin package maintainer discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Oct 2021 18:24:52 -0000 Ken Brown via Cygwin-apps writes: > There are currently five emacs packages: emacs-common, emacs, > emacs-X11, emacs-w32, and emacs-lucid. The first includes things that > are needed by each of the other four, and those four each include an > emacs binary. The binary in the emacs package is > /usr/bin/emacs-nox.exe. The other packages contain > /usr/bin/emacs-X11.exe, and so on. > > This way of naming the packages doesn't really reflect the contents of > the emacs package. It also means that anyone who installs emacs gets > emacs-nox.exe, even if they plan to use one of the other three > binaries. > > I would rather rename the current emacs-common package to emacs and > the current emacs package to emacs-nox. But then the new emacs would > have to have a way of requiring the installation of at least one of > emacs-nox, emacs-X11, emacs-w32, or emacs-lucid. Is there any way to > do this with our current setup machinery? I don't think we have the transaction capability that would be necessary to specify that the meaning of an already existing package name (two, actually) changes in this manner. You might have to use new package names and place the appropriate obsoletions w.r.t. old names instead. > My idea three years ago was to have the new emacs package require a > "feature" called, for instance, emacs-bin, and then have each of > emacs-nox, emacs-X11, emacs-w32, emacs-lucid "provide" that feature. I have no idea if multiple packages can provide the same feature. It's worth trying if it does what you want (you must pick at least one of those). What I'm reasonably sure we currently don't have is packages providing the same feature, but conflicting among each other (you must install one and only one package that provides the feature). What calm thinks of that is another thing entirely, I'd say. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Terratec KOMPLEXER: http://Synth.Stromeko.net/Downloads.html#KomplexerWaves