Il 08/02/2018 16:04, James Le Cuirot ha scritto:
Citing Kenneth Hoste at FOSDEM this year: modifying a package
without changing its version is a bad idea.
His presentation was very good (video included):
https://fosdem.org/2
018/schedule/event/how_to_make_package_managers_cry/
This isn't so clear cut simple. We build from source at user systems.
Think of the effect for something like webkit-gtk, chromium,
libreoffice, etc.
Exactly and while this package isn't as big as those, it could be
argued that xorg-server is bumped frequently enough that the lingering
dependency would have been flushed out soon enough anyway. It's not
like it's doing any harm.
I also think that FOSDEM talk was making a different point, aimed at
upstreams in order to help packagers rather than packagers themselves.
Thanks for the information and sorry for the noise.
I wasn't fully aware of the meaning of the --dynamics-deps and --changed-deps
option.
I am still not entirely convinced that changing a package after it is committed
to the repository cannot do harm: even as a user, I would like to know when and
why a package's dependencies changed.
But I don't maintain packages so my opinion is not very relevant, and the
gentoo guidelines indeed allow to change the dependencies inline.
Michael
