You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The init command is somewhat odd. In the current implementation, all it does is read components.yaml and create the state (.mepo/state.pkl). In the original design, it was meant to be followed by mepo clone. Since clone now has init folded in (i.e. has the ability to initialize the state), the standard way of using mepo is to start with the clone command
mepo clone -b <version> <url> <directory>
So it is possible to use init for some other purpose. For example, it can traverse a directory tree that has been manually prepared, find .git directories and create the registry (components.yaml), thereby initializing a mepo repository.
The text was updated successfully, but these errors were encountered:
The
init
command is somewhat odd. In the current implementation, all it does is readcomponents.yaml
and create the state (.mepo/state.pkl
). In the original design, it was meant to be followed bymepo clone
. Sinceclone
now hasinit
folded in (i.e. has the ability to initialize the state), the standard way of usingmepo
is to start with theclone
commandSo it is possible to use
init
for some other purpose. For example, it can traverse a directory tree that has been manually prepared, find.git
directories and create the registry (components.yaml
), thereby initializing amepo
repository.The text was updated successfully, but these errors were encountered: