Date: Sat, 20 Jan 2024 14:44:36 +0100 From: Mathieu Arnold <mat@freebsd.org> To: Vladimir Druzenko <vvd@freebsd.org> Cc: Daniel Engberg <daniel.engberg.lists@pyret.net>, ports-committers@freebsd.org, dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org Subject: Re: Re: git: 589aaaeb09b7 - main - multimedia/libvpx: update 1.14.0 Message-ID: <q6fstboxxhifooaltp7xcs2xakpjcrwcglpx5mia5xztvn2bpp@yrlcp6x5ie4k> In-Reply-To: <c64f6d1e-3911-4336-947b-18c37a6b2546@freebsd.org> References: <202401200042.40K0gNmu053279@gitrepo.freebsd.org> <240f4c88-582d-4da4-ba92-50d11ddfade3@freebsd.org> <m5bjygorxxilrvtyoqmb54ablzs4tjiocvfjjzskoffipyjlqb@7ap2zou7cm3q> <6e13868f-8910-4468-9e1d-2a231a0723ca@freebsd.org> <4690f8987d3a0841ee7105d989847d1c@mail.infomaniak.com> <c64f6d1e-3911-4336-947b-18c37a6b2546@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--e66ix5axsylsw5nn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jan 20, 2024 at 03:22:17PM +0300, Vladimir Druzenko wrote: > For example table in wiki with rows:| planned date | port | so name for b= ump > | the date the entry was added to the list| > Or file "BUMPS" in root of the ports repo near MOVED, UPDATING and CHANGES > with same fields. > Remove row after commit bump to main. > It's for real mass bumps like poppler, icu, libvpx, opus, webp, ffmpeg, > rust, maybe perl5 or change default python and etc. How does filling in that table work exactly ? I mean, the only way that can work is if upstream is actually you and you know that you have decided to release a new version of foobar in 3 days and 12 hours, then you can add to that table "dependants of foobar will et a revision bump at xxx". And then, for it to be usefull, you need to find some other committer of a port that is also a dependency of a port in your list, and that is also upstream, to synchronise its clock with yours so that you only bump that shared reverse dependency once. It is not worth the trouble. In all other cases ports gets updated when the committer (who is doing that work as a volunteer is their free time) gets to it. We all do our utmost to keep things working, and it does not really matter to us if the package builders have to rebuild most stuff every couple of days, they do it everyway. It's a nice thought experiment that might work in in a controlled corporate setup, but it is absolutely pointless where 300+ unpaid volunteers work in an asynchronous way whenever they have the time. Ports get updated, when that port provides a shared library that changes, then ports that depend on that library gets bumped, that's it. If it happens that one of those ports has two library it needs that get updated over two days, that's life, it's what chaos theory is about. --=20 Mathieu Arnold --e66ix5axsylsw5nn Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQITBAABCgB9FiEE9XJBpJetWizkEBUef2IOCp6dQb4FAmWrzkNfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEY1 NzI0MUE0OTdBRDVBMkNFNDEwMTUxRTdGNjIwRTBBOUU5RDQxQkUACgkQf2IOCp6d Qb5FBwwAmx4/3RdK3hE7ILsmWW6vbK4LTb/hmlvDsecMfQE+X5M97LKTkTQC+RGf TEFFcCbrR55XHBecpmG1PUwgKGDDXqV2LbeWS0HCOKZOD21mp/qf98P7EtpQn4Ef /yTDvNn95bQeW2zmRr3CP7ERx04MD5vWfhxGZPe6oNBzwziaWOmsWXKhYH34s448 iZyvviDii5Os1TJ36WNfjVG/4rGdFaGQPhueEwx8aLHaOzTHE3krer+ELonYwjiT 8JLGDSfkMVxZolX2GSGOovF1CLPAOflD+gEdlzB4NOyPqnkEiXEKR4BFivxK/0jS trF2jGMLqPHWa0ArrIN+alt6FZzRcF1MA4P1jv1vAEmB1Zdetqu5bOJDp2oYCxJ9 os0IjkzrtdcHCDBabInGZbqjipFW3ICaHmfx4ieKewlRZnfs3Q3YEqXHGCkykl72 KlbjTB95C3cqoHc05dUJK2ZPjkBdrY+EPVbhDAyslGZvDLrDr4pxUUgy4Kp7Sebp uNyxhjeP =3tOn -----END PGP SIGNATURE----- --e66ix5axsylsw5nn--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?q6fstboxxhifooaltp7xcs2xakpjcrwcglpx5mia5xztvn2bpp>