On 18/02/2025 14:45, Colin Watson wrote:
On Tue, Feb 18, 2025 at 01:44:35PM +0100, Nicolas Peugnet wrote:
Maybe it would be good to have an entry in the NEWS.Debian file?
NEWS.Debian entries should be user-focused. So if you write one (I
don't know whether it makes sense), it should be about things like
incompatible changes that a user of the package would need to know
about, as opposed to internal details such as which language the package
is now written in.
So about this, reading Docker Compose's migration docs [1], one of the
most disruptive change seems that previously the command was run as
"docker-compose" and now as "docker compose".
I was thinking that we should add something similar to what is explained
in the "What does this mean for my projects..." section:
For most projects, switching to Compose V2 requires no changes to the Compose
YAML or your development workflow.
It's recommended that you adapt to the new preferred way of running Compose V2, which is to use
"docker compose" instead of "docker-compose". This provides additional
flexibility and removes the requirement for a docker-compose compatibility alias.
However, Docker Desktop continues to support a "docker-compose" alias to redirect
commands to "docker compose" for convenience and improved compatibility with third-party
tools and scripts.
It is already quite good as is, but I did not understand at first that
the alias was not provided by the Docker packages, and it was the users
that had to add it themselves. I think we can be more precise than this
and explain that one needs to create the alias.
[1]
https://docs.docker.com/compose/releases/migrate/#what-are-the-differences-between-compose-v1-and-compose-v2
--
Nicolas Peugnet
