Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 23 Sep 2020 08:53:15 +0200
From:      Baptiste Daroussin <bapt@FreeBSD.org>
To:        Mikhail Teterin <mi@FreeBSD.org>
Cc:        ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org
Subject:   Re: svn commit: r549657 - in head: graphics/digikam graphics/libbpg graphics/libheif multimedia/ccextractor multimedia/emby-server multimedia/ffmpeg multimedia/gstreamer1-plugins-x265 x11/xpra
Message-ID:  <20200923065315.6xaqwxvljkhj646s@ivaldir.net>
In-Reply-To: <202009230417.08N4HCAn072615@repo.freebsd.org>
References:  <202009230417.08N4HCAn072615@repo.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--k7zq7h2bct2tjhp7
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Sep 23, 2020 at 04:17:11AM +0000, Mikhail Teterin wrote:
> Author: mi
> Date: Wed Sep 23 04:17:11 2020
> New Revision: 549657
> URL: https://svnweb.freebsd.org/changeset/ports/549657
>=20
> Log:
>   For well over 10 years portmgr@ have been promising to remove the
>   ridiculous need to bump PORTREVISION of depending ports, whenever a
>   dependency is updated, but here we still are...
>  =20
>   Bump PORTREVISION for the 9 users of x265 now that it has been
>   upgraded from 3.2 to 3.4.
>=20
I have been in portmgr@ for around 10 years such promise has never been mad=
e!

It would be nice to refrain sarcastic comments like this one!

Aside from that it is up to everyone to work on the infrastructure, portmgr=
 is
there to ensure it is done a consistent way, it is not up to portmgr to do =
the
work, it appears some members of portmgr are often doing the infrastructure=
 work
but that is all.

That said the number of bumps that are required have been reduced a lot in =
the
last 10 years, and the fact that the SOVERSION of a library changes makes it
requires the bump as it changes the binaries linked to it!
If you have a technically working idea on how to automate those bumps be our
guess, propose a patch. In the mean time I would really appreciate if you c=
ould
be a bit more respectful.

Best regards,
Bapt

--k7zq7h2bct2tjhp7
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAl9q8NsACgkQY4mL3PG3
PlpJHA//a3f+ZHxc8lCr7rjvCF2B9H25Qa34Eu0N70cXO81QgWPDF2qVQuCC6a+u
CFD5HKq4ZAlg7XwSPbPFGYKU9jli13sGRujqMG1XarbbKF7rzedSr+U5K0OqbzYJ
PZ/3EilkqJvFES/D/99lX5CNv3FQhE1AZ+J1dnVV2EuRrTY3VN/yleN+0LJo045c
IMvDKU2LOKRnTqyOshO1RqwKgZnJJN9OiGCS5C0xLZcDBC7xlAWgnQI4bbb89vxa
9enpJQ8eFOrkQdAjNAUGugblTmOG8l8D/AMY7vdEHixotprKwm178cFgqVdGKSN1
P38l1U2VcEjcC0PlvrKqhsFrn7PQtQdkMbMLe2fHPMG3cWk4T6v2BRgCGQJtvo4l
3No8UImaSvtXBIuqGVu/YF5BjjGPeaYCzXbeDWIr2xE72+jorM1D5Bhq1pvIL3GP
DNqwAeEtsbSCJrgAPCVkrK4Z9yA8o6gaHwhi5HsYwGMiVm1gDTJ+UcafsVfaAE3D
KHsPV7fEQN57xUDFSliha8bDeXjaA6l1GAY8oySexoC20kbGn4tYg4IKgTwMJ6Y2
k78axb6Od9hsTVfE3PanjhO4nE1hKUl31wi/hAqj53cfmNIrLtWfI/tIuCIX5rKY
ESSCvEXRi5/Wn19/REvevjEuO4UPG9g3kcF8MwReqcbodifwReo=
=Meaw
-----END PGP SIGNATURE-----

--k7zq7h2bct2tjhp7--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200923065315.6xaqwxvljkhj646s>