X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Message-ID: <20201219211448.24154.qmail@stuge.se> Date: Sat, 19 Dec 2020 21:14:48 +0000 From: "Peter Stuge (peter AT stuge DOT se) [via geda-user AT delorie DOT com]" To: "Peter Stuge \(peter AT stuge DOT se\) \[via geda-user AT delorie DOT com\]" Subject: Re: [geda-user] Problem with Guile 2.2.4 dependency for gEDA 1.10.1. References: <20201219180603 DOT 22277 DOT qmail AT stuge DOT se> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk Roland Lutz wrote: > On Sat, 19 Dec 2020, Peter Stuge (peter AT stuge DOT se) [via > geda-user AT delorie DOT com] wrote: > > You need to encode the *actual* minimum required dependencies in > > configure.ac, not what your particular testing environment uses. > > How do I know what the "actual" minimum required version of a dependency > is? It's the first version where all used APIs are available and functional. When inheriting a project it may require unmanageable effort to determine those for all used APIs, in that case it's a good strategy to at least only ever bump required versions in commits which add some code that uses an API not available in the previously required version. The various GNOME projects are good at documenting first-available-version in their API documentation, but sometimes it sadly does become neccessary to search for that first version manually, when adding code which uses an API for the first time in a project. //Peter