Freeciv

My impression was that apt-get isn't going away, but its interface has been stabilised for low-level script use; and apt is the recommended human-facing tool (and they want freedom to make backward-incompatible changes in future).

From apt(8) on my system:

SCRIPT USAGE AND DIFFERENCES FROM OTHER APT TOOLS
       The apt(8) commandline is designed as an end-user tool and it may
       change behavior between versions. While it tries not to break backward
       compatibility this is not guaranteed either if a change seems
       beneficial for interactive use.

       All features of apt(8) are available in dedicated APT tools like apt-
       get(8) and apt-cache(8) as well.  apt(8) just changes the default value
       of some options (see apt.conf(5) and specifically the Binary scope). So
       you should prefer using these commands (potentially with some
       additional options enabled) in your scripts as they keep backward
       compatibility as much as possible.

Interesting... when my Debian was initially updated after Buster release, there was some problems with 'apt-get' not working properly, and discussions about the solution I found had many comments that people simply shouldn't be using outdated apt-get any more, but should have migrated to apt already. But I don't what is the position of those people in the Debian project, or how well informed they are.

Is there a reason for installing dependencies in the build script rather than using travis' addons: apt: packages? If not we could move depependency installation there and have travis handle apt vs apt-get

Sveinung Kvilhaugsvik wrote:

Is there a reason for installing dependencies in the build script rather than using travis' addons: apt: packages?

Not that I know.