[question] Documentation on conancenter fork: conan export for dependent packages necessary?

[The documentation on forking conancenter](https://github.com/conan-io/docs/blob/5f5410b9da809366b4ee8ac120bdf47d4e25dd24/devops/conancenter/hosting_binaries.rst?plain=1#L11) says "Create a script that first ``conan export`` all the packages in your list", where "list" is "a list of the packages and versions you need for your project". I wonder if this is entirely correct.

To my understanding, `conan export` of all possible dependencies of the packages in "your list" would be needed. Otherwise, the recipe for a dependency of a package and version from "your list" could be missing, couldn't it be? Therefore, `build=missing` wouldn't work, because the recipe of said dependency is not available.

E.g. libtool is needed to build libest, however my list would typically only include libest.

If this actually an error in the documentation, what workflow do you suggest instead? Find out and add dependencies (possibly specific to settings, e.g. the OS) to the list as well? It could get more complex when dependencies are version specific.

Or first export all conancenter recipes to the local cache? Which takes some time.