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: [ELPA] New package: triples Date: Thu, 27 Oct 2022 11:34:51 -0400 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="35150"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: emacs-devel@gnu.org, Tom Gillespie To: Andrew Hyatt Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Oct 27 17:38:20 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 1oo4xY-0008tI-Cy for ged-emacs-devel@m.gmane-mx.org; Thu, 27 Oct 2022 17:38:20 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oo4uR-0005Ft-Bs; Thu, 27 Oct 2022 11:35:07 -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 1oo4uP-0005Fi-8i for emacs-devel@gnu.org; Thu, 27 Oct 2022 11:35:05 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oo4uK-0007QT-TK for emacs-devel@gnu.org; Thu, 27 Oct 2022 11:35:05 -0400 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id CA963440BE3; Thu, 27 Oct 2022 11:34:55 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 27834440B04; Thu, 27 Oct 2022 11:34:54 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1666884894; bh=CILNJyuBD2iJ+aoxg8XuwpV6Srncj2U/z++VMd7KETQ=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=a9QkTXVscV6hI3nlkG1XQvNTxkub65OVv3NB6TTO5//qKqya8mcDMmr4gJ4TCzDsa E7QkI5g7Sbj59UZyEQOGQ8Z+9nn0q/U8M+gRm33k/uoII/QPhoH3LwKxtD94010DOy crCGODfmqoKMc6rOUQPBsCFTrwQAqL3V3hGI1Wi7z3t8Y+vosaRmp6jE8q1KnKr+zo UqM/4Y5PB0oCg0sYtB+r2erXfBM1RQ2O3GOtVK2iCruq157clAILIzpOs4SGZ02V42 xvoJFtM5NMZjbvH63QQLKTvln08lJZ8UnWiDRZ4oCfQWk2QTSqAp74wBtZW4tRGDs1 bcZ635RbvXJ9w== Original-Received: from alfajor (unknown [45.44.229.252]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id DE501120F7A; Thu, 27 Oct 2022 11:34:53 -0400 (EDT) In-Reply-To: (Andrew Hyatt's message of "Thu, 27 Oct 2022 01:15:10 -0400") 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 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: , Original-Sender: "Emacs-devel" Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:298628 Archived-At: > About the possibility of using one or the other, whichever is available, how > would that work in terms of package dependencies? I don't think it's > possible to have an OR dependency specified in the package-dependencies > line in the source, but really only one of emacsql or emacs29 would be > required. If you have any insight into this, it'd be useful. Package dependencies just tell the package manager to install other packages to try and make it easier on users to get a working package. But you don't need to have a precise/exact description of the real dependencies in the `Package-Requires` (as long as the correct byte-compilation of your package actually depends on some other package, e.g. if your package uses a macro defined in the other package). You can just remove the `emacsql` dependency from `Package-Requires` and replace it with a runtime check for the presence of either `emacsql` or the new sqlite support that emits an error when applicable (with a message explaining to the user that they need to have one of those two thingies before they can use the package). [ Just make sure the error is not emitted just because the file(s) from your package are loaded, but only when some code is actually called. ] Stefan