This is exactly what I wonder about. I understand it may not be straightforward, and operability of the ecosystem has a higher priority. But the very fact that we switched to Pkg3 lead me to think, maybe mistakenly, that such piece should already be in place.
Well, to create a package, according to the manual, you should run through the
add commands to properly prepare the
Manifest.toml files. But to register it you should throw away those files and prepare a
REQUIRE file instead. Am I the only one finding this unintuitive?
Also, with Pkg3 it is possible to declare a dependency on an unregistered package, but AFAIK there is no way to declare such dependency in
REQUIRE. So I can’t deploy a registered package depending on an unregistered one.
As already noted no one here is complaining, and i believe this discussion already clarified the underlying problem, namely that we miss a “replacement system”, i.e. a
My very humble opinion and proposal, is that these facts, and the natural consequence that we can not take full advantage of all Pkg3 functionalities for registered packages, should be clearly stated somewhere in an official documentation, rather than being scattered in several posts on the Discourse.
Besides, if there was such entry in an official documentation, @Tamas_Papp would not have started this discussion, and I would have been aware of the missing “replacement system” problem.
Sorry for cluttering this discussion with questions due to my ignorance, hopefully this would be useful to someone else.