Bug 905849 – No guide on proper testing darwin prefix packages

• Product: Gentoo/Alt
• Status: CONFIRMED ---

[Description Andrey Aleksandrov 2023-05-07 01:20:36 UTC]

At the moment there is no stable keyword for Darwin prefix. Only ~x64-macos and ~arm64-macos available. I don't want use these keywords by default, because it leads to using unstable or even broken packages. When something breaks I can't be sure if its because of package itself or maybe there is something wrong with @system.

I decided to test @system and see if it's possible to add stable arm64-macos keyword to existing arm64 packages. I followed this guide to setup testing environment: https://wiki.gentoo.org/wiki/Package_testing

Turns out pkg-testing-tool completely broken because it doesn't respect EPREFIX path.

Configuring fails with "C compiler cannot create executables" when I set LDFLAGS="${LDFLAGS} -Wl,--defsym=__gentoo_check_ldflags__=0" as guide says.

It's impossible to run coreutils test because it requires strace which requires linux-headers. And of course linux-headers blocked, there is no point to use it with Darwin.

I managed to test tar, only one test failed: "151: time: tricky time stamps". I don't see a way to check if it's okay for this setup or I need to report it somewhere. What should I do about it?

So. My question is. How to properly test prefix packages on macos? Is there a doc I failed to find or something? How current testing of system packages happens when coreutils requires linux-headers?

[Comment 1 Benda Xu 2023-07-26 03:44:57 UTC]

It is in an experimental state.  Make the ebuilds merge is already non-trivial.  We have not advanced to the test-everything stage yet.

[Comment 2 Sam James 2023-07-26 03:51:20 UTC]

(In reply to Andrey Aleksandrov from comment #0)
> At the moment there is no stable keyword for Darwin prefix. Only ~x64-macos
> and ~arm64-macos available. I don't want use these keywords by default,
> because it leads to using unstable or even broken packages. When something
> breaks I can't be sure if its because of package itself or maybe there is
> something wrong with @system.
> 
> I decided to test @system and see if it's possible to add stable arm64-macos
> keyword to existing arm64 packages. I followed this guide to setup testing
> environment: https://wiki.gentoo.org/wiki/Package_testing
> 
> Turns out pkg-testing-tool completely broken because it doesn't respect
> EPREFIX path.

Please file a bug for that if you didn't already.

> 
> Configuring fails with "C compiler cannot create executables" when I set
> LDFLAGS="${LDFLAGS} -Wl,--defsym=__gentoo_check_ldflags__=0" as guide says.

Right, I don't know if this works with the macOS toolchain.

> 
> It's impossible to run coreutils test because it requires strace which
> requires linux-headers. And of course linux-headers blocked, there is no
> point to use it with Darwin.
> 

I suspect it doesn't really need strace and the dependencies need fixing (and/or a test needs skipping).

> I managed to test tar, only one test failed: "151: time: tricky time
> stamps". I don't see a way to check if it's okay for this setup or I need to
> report it somewhere. What should I do about it?

I wouldn't expect any test failures. You can file a bug here first then raise it upstream.

> 
> So. My question is. How to properly test prefix packages on macos? Is there
> a doc I failed to find or something? How current testing of system packages
> happens when coreutils requires linux-headers?

Just run test suites, I think.