Aria Desires

> random thought: is any of this config per target or is it always per installer/dist mechanism yeah it's an open question to me if/how that would be supported. `[build.target."x86_64-pc-windows.msvc".cargo]...

Biggest first step is pulling axoproject in-tree so it's easy to work on config and no need for fake separations of concern.

TODO: write an example TOC of the new config

Currently we have: * `generate-ci github` which generates CI scripts to: * wait for a git tag to be pushed * creates a Github Release * spins up tasks that...

After #115 the installers are now totally factored out to just take "the download URL for the dir to fetch things from" and [the github-ci code is increasingly factored out](https://github.com/axodotdev/cargo-dist/blob/81d948c4df766e56d3d5c9d6a6a8cbe4548d380d/cargo-dist/src/ci.rs#L39)...

That does indeed seem not-quite-right. I know this condition has gone through a lot of evolution, and has some really specific subtleties around the publish-a-library-which-skips-the-build-steps-but-still-runs-later-steps usecase. This condition also used...

makes perfect sense! I wonder if the linkage checker can detect this so we know to automatically include the dll 🤔

Oh! Thanks for the additional context that you specifically interested in MSIs here -- some additional work may also be needed to teach MSIs to do additional includes: https://github.com/axodotdev/cargo-dist/issues/543

Yeah including more than just the one file should require you to [set a custom install-path](https://opensource.axo.dev/cargo-dist/book/reference/config.html#install-path), but we need a clear story for how to specify whether your custom install...

Asking some rust toolchain experts what the Correct approach is