On Sat, Aug 29, 2026 at 1:50 PM Daniel Sahlberg <[email protected]> wrote:
> Den lör 29 aug. 2026 kl 13:42 skrev Stefan Sperling <[email protected]>: > >> On Sat, Aug 29, 2026 at 12:27:43AM +0300, Pavel Lyalyakin wrote: >> > My focus is the INSTALL document. The mention of get-deps.sh in the >> > document looks like a historical artifact and, frankly, it confused me a >> > lot to start this email thread. Getting the dependencies is quite simple >> > today, so I'd remove the get-deps.sh summary and its other mentions from >> > INSTALL entirely, replacing it with the steps for installing the >> > dependencies via a package manager and link to the official download >> pages >> > of the dependencies. >> >> I agree with removing get-deps.sh. What it is doing can be done manually. >> And get-deps.sh does not even perform checksum verification of downloaded >> artifacts before extracting them, which is relatively unsafe. >> >> One use case of this script might have been developers quickly building >> Subversion and its major dependencies from source code. These days, for >> developers I would recommend tools/dev/unix-build/Makefile.svn instead. >> That script is maintained, fairly up-to-date, and verifies checksums. >> > > I agree with Stefan. How about: > 1. Remove the notes about get-deps.sh from INSTALL and backport to the > 1.15.x branch > 2. Add a "deprecated" note to get-deps.sh and backport to the 1.15.x branch > 3. Declare get-deps.sh deprecated in the 1.15.x release notes > 4. Remove get-deps.sh from trunk (effectively removing it from 1.16) > Sounds good to me. > > The purpose of 2 is to try to catch anyone using get-deps.sh and point > them to the future removal. > > Should we mention something about Makefile.svn in INSTALL? As Stefan says > it is maintained and very useful if you want to build Subversion with > different dependencies. > > > I personally think the scripts for building dependencies are usually confusing. They are often environment specific. That's why I believe the user should provide the libraries to the build system from the distribution/package manager/or make customisation that they want by themselves. Maybe I'm wrong about it though. But on most of the modern Unix systems there is no need for it. -- Timofei Zhakov
