Hey Bryan,
as discussed on IRC, I'd like to have information about what latest ports repo commit ID were the binaries in the pkg database built from.
The reason for it is, I could set my local poudriere ports repo to that commit, thus avoiding having to rebuild packages with huge resource hogging compilations, that are dependencies of packages that I build with it.
For clarification, here's a recurring example that is now happening again: rust. It currently has 1.92.0 in the binaries and 1.93.0 in the ports tree, which makes poudriere rebuilding it (with the aforementioned resource hogging), only to use it to compile clamd, that depends on it.
data.pkg/data could have an extra key with latest_ports_commit or something along these lines that I could extract, and then set my local ports repo to it. That way I could avoid going my production server crazy. :)
Thanks in advance!
Regards,
László
Hey Bryan,
as discussed on IRC, I'd like to have information about what latest ports repo commit ID were the binaries in the pkg database built from.
The reason for it is, I could set my local poudriere ports repo to that commit, thus avoiding having to rebuild packages with huge resource hogging compilations, that are dependencies of packages that I build with it.
For clarification, here's a recurring example that is now happening again: rust. It currently has
1.92.0in the binaries and1.93.0in the ports tree, which makes poudriere rebuilding it (with the aforementioned resource hogging), only to use it to compile clamd, that depends on it.data.pkg/datacould have an extra key withlatest_ports_commitor something along these lines that I could extract, and then set my local ports repo to it. That way I could avoid going my production server crazy. :)Thanks in advance!
Regards,
László