On 2025-11-10 02:04, cen wrote:
With 30000+ ports that can build 37000+ port-packages, I doubt anyone knows which ones can produce byte-for-byte exact matches from correctly matched inputs vs. which ones cannot overall. That likely could be a whole research topic of its own.This is exactly what I want to find out. :)I also do not know if port-package files (.pkg) would always match in cases where the installed materials would be a byte-for-byte match. Those two are not the same thing. Which are you after? Both types?The main goal is this: If I install a package XYZ can I rebuild it locally and get the exact same output, bit-by-bit identical.The build environment being as close to upstream build environment is a prerequisite to achieve that goal. It does not necessarily mean it has to be 100% identical though, some differences may be forgiving.
Unless I'm missing something, wouldn't using poudriere with the same make.conf as the package builders and default options from the same git build give *functionally* identical packages?
I don't have a need for identical packages but I find it useful and elegant to check the git build level being used by the package builders, checkout the same build then build my few packages and dependencies locally. That way I get my options included in my packages where necessary but the rest of the packages are unaffected. Doing this for the whole tree with default options throughout should get the OP what he needs. Yes? Or have I misunderstood what is needed?
HTH, Simon.
OpenPGP_0x3E276F607A844457.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
