Skip to content

Conversation

JamiKettunen
Copy link
Contributor

Without this one had to do something like echo a | build_packages.sh --mw, but we might as well include a flag that does the same thing.

Without this one had to do something like 'echo a | build_packages.sh
--mw', but we might as well include a flag that does the same thing.
@Thaodan
Copy link
Contributor

Thaodan commented Jan 30, 2022 via email

@JamiKettunen
Copy link
Contributor Author

@Thaodan why not a third option: keep current behavior of the script but add the tweaks of this PR behind --mw=all? I can see how the interactive option is useful as well for some people due to MW package builds breaking somewhat often, so then that package can be reset back to a known working version, run --mw and choose no for most except all when the previously broken package shows up again, then the script continues to build the remaining MW in order.

@sledges
Copy link
Contributor

sledges commented Feb 1, 2022

Here's 4th option: add -y, --non-interactive global switch and latch from MW side (later other parts can also take use easily), also the short cmdline gets simpler: -ym instead of -m all

@Thaodan
Copy link
Contributor

Thaodan commented Apr 29, 2022

That would work, I think the default should be what is used most.
Building all or just building some?
I think building all in that case asking if I really want to do that is annoying.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants