I would like to hear the recommendations for creating a new package “properly”. From my questions, you will see that I don’t fully understand what a package is, especially compared to a (collection of) module(s).
For example, should a package always have a “main” module, or could it have several modules on equal footing? In fact, must there be a module bearing the same name as the package?
I heard that it’s bad form to have submodules within a module, is it equally bad to have several modules in a package? (surely not…?) Are the different modules always meant to include one another automatically, or is this sometimes left to the user of the package?
Generally speaking, I feel that should simply know more about packages and what they are – a little beyond “a package is like a module which you can download with the package manager”
Say I start working on my own package, and for the moment there is really just one module, and having the thing on Github is only in the far, far future. Should I really prepare a package already, or just work on a module for the moment?
The example uses of the Revise package seem to assume that people create a new package as a matter of routine, even just to try out a couple of ideas… this is puzzling to me.
I have not found much in the documentation about packages, but perhaps I’m not looking at the right place.
any help appreciated!