Current practice for specifying custom target dependencies?

General Usage
, ,
1

I’m looking to specify extra dependencies for code in an ‘example’ dir and separately for code in a ‘benchmark’ dir of a package. Akin to how ‘targets’ and ‘extras’ works for test dependencies.

Early discussions I saw around Pkg mention custom ‘targets’ as a future solution, e.g. Aug '18 discussion

It looks like specifying custom targets is valid, but Pkg doesn’t currently do anything with targets other than test, and whether or not to use ‘targets’ and ‘extras’ or separate manifest files for custom targets is not totally resolved, e.g. JuliaLang/Pkg.jl#624 & JuliaLang/Pkg.jl#744

First, are there further developments on the topic that I missed here?

Second, any suggestions or examples on providing custom deps in the appropriate context, either that help when distributing packages or just in a local-dev context?

2

See https://github.com/JuliaLang/Pkg.jl/issues/1233

2 Likes
3

Thank you. #1233 and links therein cover both direction and the current state of affairs.

If anyone has anything smoothing over current workarounds, e.g. keeping distinct .tomls from diverging, please do share.