Date: Sat, 20 Jan 2024 12:10:28 +0100 From: Mathieu Arnold <mat@freebsd.org> To: Vladimir Druzenko <vvd@freebsd.org> Cc: 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: <m5bjygorxxilrvtyoqmb54ablzs4tjiocvfjjzskoffipyjlqb@7ap2zou7cm3q> In-Reply-To: <240f4c88-582d-4da4-ba92-50d11ddfade3@freebsd.org> References: <202401200042.40K0gNmu053279@gitrepo.freebsd.org> <240f4c88-582d-4da4-ba92-50d11ddfade3@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--jyrgmivdc6wwj26u Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jan 20, 2024 at 12:07:03PM +0300, Vladimir Druzenko wrote: > Can we make some kind of schedule for mass bumps of huge ports? > Users who build from ports can schedule upgrade and prevent build somethi= ng > very big "2 days in a row". > Even if you use binary packages, updating for example virtualbox will ent= ail > a restart (savestate/start) of all virtual machines, and this must be > planned in advance. > If this already exists, please point to it. > Thanks! Hi, I am not sure what you are complaining about. On the one side, it seems that you want to build things yourself and to have everything up-to-date and you upgrade every day. On the other side it seems that you would like to have things not updated so you don't have to rebuild things every day. If you absolutely want to upgrade every day by yourself, then, well, you have to expect to rebuild things, large and small two days in a row once in a while... Use binary packages, there, I fixed the rebuild every day problem you have. Then you say that if virtualbox gets an update, you need to restart your virtual machines, and that it is a problem. Well, it is only a problem if you have the absolute need to upgrade as soon as possible. And in that case, it is your problem. Most of the time, the virtualbox updates are not critical security issues and they can be planned on your side for when it is convenient for you. In any way, nobody forces you to upgrade as soon as there is an update of a port, but in the same way, nothing is going to force the rest of us to not commit to ports because it is inconvenient for you... --=20 Mathieu Arnold --jyrgmivdc6wwj26u Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQITBAABCgB9FiEE9XJBpJetWizkEBUef2IOCp6dQb4FAmWrqiNfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEY1 NzI0MUE0OTdBRDVBMkNFNDEwMTUxRTdGNjIwRTBBOUU5RDQxQkUACgkQf2IOCp6d Qb6QXAv/TaRVM/Pav9I3w8athPKOlH3k4BZSWfRMHSeNzIa3yBjF2gxSJbdslotR 3ZIwlnerGj3q84adHxzfq3U9JkbMQ8WQlPd+EChI+eIJTsFrpCG5+PW3nnfzwl5+ VtPtAhWJmQ4xLI0wf7SKTC3QmUbeeDi8pP1goGAAbEWhhGFFtSdDElCMZv1IBQyx 18XMF+jjpb21Frf781XlUxvoYIuyV/mbSvwAszvMJ7Ql7raFaGhuMpaatF2wdnTH uGYKXOcrx8LnnI9+9IwDWIBiojElvEyRsF0rFC/aigUjSCE4vm2xNpDv6ehAeCP1 S2TOGkdv/KkyroGk3GWc8PO85Gjhm8knqWlkiYb6Gy9WjIfNCNL3gPSpz0TigjdT AwlgE02foLJTAX+QEoyuz5zPsHugG9pMPBoWnccd4om70bPlR1yXn5t2tswNiwf7 pG+6FBwjfK25ZV8+KGONpCIwGGhlkHhvXLbSXuI/lX+vNOM85sgVRkuu1FCCG9IQ 2ugHf4mg =s2+C -----END PGP SIGNATURE----- --jyrgmivdc6wwj26u--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m5bjygorxxilrvtyoqmb54ablzs4tjiocvfjjzskoffipyjlqb>