should support GO_ENV and related flags from Mk/Uses/go.mk #32

dch commented 2025年03月30日 14:21:30 +02:00

Is there a way in general to leverage the information already in Mk/Uses/* and not need to duplicate
it in portfmt as well?

Is there a way *in general* to leverage the information already in Mk/Uses/* and not need to duplicate it in portfmt as well?

tobik commented 2025年04月03日 18:10:43 +02:00

Is there a way in general to leverage the information already in Mk/Uses/* and not need to duplicate
it in portfmt as well?

If Portfmt ever learns how to expand macros then maybe? But a list/ordering of manually curated user-settable variables would be needed anyway for merging variables and portclippy. There could be tooling to help maintain that list. The list should live in the ports tree as well instead of being hardcoded in Portfmt, see #25

Anyway GO_ENV etc were added on the release/1.1 branch.

> Is there a way in general to leverage the information already in Mk/Uses/* and not need to duplicate it in portfmt as well? If Portfmt ever learns how to expand macros then maybe? But a list/ordering of manually curated user-settable variables would be needed anyway for merging variables and `portclippy`. There could be tooling to help maintain that list. The list should live in the ports tree as well instead of being hardcoded in Portfmt, see https://codeberg.org/tobik/portfmt/issues/25 Anyway `GO_ENV` etc were added on the `release/1.1` branch.