Date: Fri, 9 Jun 2023 07:50:35 +0900 From: Tatsuki Makino <tatsuki_makino@hotmail.com> To: Dave Cottlehuber <dch@skunkwerks.at>, FreeBSD Ports <ports@freebsd.org> Subject: Re: git sha of ports tree used to build packages from Message-ID: <PSAPR03MB56397DB5AAFE8446182C8BB9FA50A@PSAPR03MB5639.apcprd03.prod.outlook.com> In-Reply-To: <25172546-9130-4cae-acf6-4b6baf7c9c6c@app.fastmail.com> References: <25172546-9130-4cae-acf6-4b6baf7c9c6c@app.fastmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello. Someone said something similar to that. :) -> https://lists.freebsd.org/archives/freebsd-ports/2023-January/003292.html It seems that the package download feature of poudriere-devel has to keep pace with the official builder. Perhaps when updates are made to chromium, etc., the official will be delayed somewhat? One of the reasons poudriere picks and chooses which packages to rebuild is that it cannot find the resulting package displayed by the following command. pkg query -F /usr/local/poudriere/data/packages/jail-porttree/All/rust-1.69.0_2.pkg %dn-%dv If rust is to use curl only for runtime linking, dynamic loading, or piping by executing commands, there would be little need to rebuild the entire rust. Therefore, if only the discrepancy in the rust package is rewritten, packages can be built without any problems :) Regards. Dave Cottlehuber wrote on 2023/06/09 00:58: > > This would be a huge help in avoiding needless local poudriere rebuilds > when my ports tree is ahead of whatever the builders have done. Nothing > like watching cmake* openjdk* llvm* rust* etc starting up when all you > really needed was some trivial leaf package.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?PSAPR03MB56397DB5AAFE8446182C8BB9FA50A>