should :wx dependency be required?

[mayel]

This is causing me issues when trying to mix release in a docker that doesn't have or need wx

[kipcole9]

I didn't reaklise that :extra_applications propagated to consuming apps. You're right, it shouldn't be a hard requirement. I'll work out a way to add it only if it's present. I assume that's your primary symptom - wx isn't compiled into your production runtime?

[mayel]

That's right, I got (Mix) Could not find application :wx when running mix release after upgrading tz_world (in a docker build using hexpm's latest alpine-based image).

[kipcole9]

I've pushed a commit to have :wx and :observer included in :extra_applications only if they exist in the runtime. Would you consider given it a spin before I release? Configure with {:tz_world, github: "kipcole9/tz_world"}.

[mayel]

sure, on it!

[mayel]

that worked 👍

[kipcole9]

Phew, glad to hear it. I’ll publish a release in a few hours (2am in my current tz)Sent from my iPhoneOn 21 Oct 2024, at 01:37, Mayel de Borniol ***@***.***> wrote: that worked 👍 —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[kipcole9]

I've published tz_world version 1.4.1 with he following changelog entry:

Bug Fixes

• Don't include :wx and :observer in :extra_applications since this propogates and :wx may not be compiled in the target runtime. Thanks to @mayel for the report. Fixes should :wx dependency be required? #43.