rev-upgrade and checking for +universal dependencies (and build dependencies)

[René J.V. Bertin]

On Thursday June 04 2015 05:02:03 Ryan Schmidt wrote:

>I believe you are correct that rev-upgrade was not designed to verify that, and does not verify that. 

It does pick up issues with library compatibility versions. I don't know how it accomplishes that, short of doing a dlopen on each binary to be tested. I'm not actually sure that *that* would catch all dyld issues, but if it does, wouldn't it be possible to let it do the check for all relevant architectures?
Supposing of course that rev-upgrade is supposed to be able to verify this aspect, but I don't see why it would not?

>You can always reinstall python27 without the universal variant and see if something breaks. 

Well, that's what I've done, and I haven't yet found any breakage. I'm just concerned that at some point this means I'll be facing a re-install of the universal variant, possibly with a whole slew of py27 packages. At least I'll know which port is responsible then...

which would inherently not need to pass on +universal? Not that installs_lib is useless, but evidently it cannot be used for complex ports like python which do in fact also install public libraries.
>
>I think depends_skip_archcheck already covers that. 

I don't think that that keyword is discussed on guide.macports, and there is the question to what extent the various depends_ versions are actually useful. I'd presume that depends_fetch, depends_extract and depends_build dependencies aren't installed when installing the binary package of a port, and I doubt that'd be the case with depends_skip_archcheck for instance. Now if there were a (documented!) `depends_build_skip_archcheck` ...

BTW: is +universal "exported" to depends_fetch and/or depends_extract dependencies too?

R.