* Initial draft of the howto for packaging an application
There's a fair bit more I think needs adding, but this has the core concepts
within it. Things still to decide or do are:
- How much lead-in and hand-holding is needed for Hatch and Poetry
For example, should we walk the reader through the `init` process for Hatch
and Poetry, and then guide them to the correct directory in which to create
their application, etc?
- How to do the example repo
Should I do two repos, one for Hatch and one for Poetry? Or should I do one
repo with a Hatch and a Poetry example within sub-directories? In either
case having a tidy one-to-one relationship with what I talk about in the
text won't be quite right.
Mainly though I feel the core of what's needed is here (and it's not much,
but has taken some testing and checking and whittling down to get here).
* Title tweak
* Add a note about declaring Textual as a dependency
While this might seem obvious, and while some tools will, as a natural
consequence of using them, ensure that this happens, it's worth highlighting
this so that the reader is mindful of this.
Also, someone might be reading the HOWTO while considering how they to this
with their own build system.
* Break paragraphs down into different lines
Just an internal layout thing. Some folk seem to like this sort of thing.
* Add a summary
* Some rewording
* Link to the example repos
* Post-initial-proof-read
* Link to pip and pipx
* Don't repeat help in the same sentence
* Remove an actual needless word
* Remove the dual use of application in a sentence
* Link to TCSS files in case the reader needs a refresh
* Explain what the example repositories were built for/with
It should be obvious from the names; but it can't hurt to be *very* clear.
* Update docs/how-to/package-an-application.md
Co-authored-by: Will McGugan <willmcgugan@gmail.com>
* Changes in response to feedback
* Trim down the into a wee bit
* Trim down the into a wee bit more
---------
Co-authored-by: Will McGugan <willmcgugan@gmail.com>
