track_features openjdk

[jakirkham]

Appears this is using track_features. Why is that? Also should it be using track_features or something else to achieve that goal?

openjdk-feedstock/recipe/meta.yaml

Lines 30 to 31 in f16da87

	track_features:
	- openjdk

[sodre]

I think this was so we could use different JDK implementations.

[jakirkham]

Makes sense. Thanks for the info.

In that case it seems like the general trend is to use a mutex package for this kind of problem. They are a bit better behaved, but they are a relatively new concept (built on existing conda/conda-build functionality). Some good discussion about this in issue ( conda-forge/clangdev-feedstock#40 ).

[sodre]

Okay, in that case I will remove the track-features set if it is okay with you.

[jakirkham]

Sounds good.

To clarify a bit, the mutex package uses track_features to indicate all non-default builds of a package as it relies on Conda's desire to minimize features. For example we might have openjdk from different vendors (Zulu, IntelliJ, etc.). If we picked one vendor build as the preferred openjdk (e.g. IntelliJ), then we would add track_features to all of the non-default builds (e.g. Zulu, etc.). These would all live in the same feedstock and all be called openjdk.