Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ck find for repositories #45

Closed
psyhtest opened this issue Oct 27, 2015 · 2 comments
Closed

ck find for repositories #45

psyhtest opened this issue Oct 27, 2015 · 2 comments

Comments

@psyhtest
Copy link
Collaborator

The ck find command for a repository returns the location of the locally stored metadata for this repository e.g.

anton@localhost / $ ck find repo:reproduce-carp-project
/home/anton/CK/local/repo/reproduce-carp-project

In most cases, however, the user will want to find the actual location of the data, not that of the metadata. Currently this can be found using the ck where command e.g.:

anton@localhost / $ ck where repo:reproduce-carp-project
/home/anton/CK/reproduce-carp-project

This is consistent with using ck find for other entities but not terribly intuitive, leading to confusion and frustration.

I suggest to change this behaviour, so that ck find returns the location of the data, while e.g. ck find --meta returns the location of the metadata. The ck where command can then be kept for compatibility or deprecated.

gfursin added a commit that referenced this issue Oct 27, 2015
…. Now "ck find repo:<name>" returns path to repository rather than to meta. To return path to meta, use "ck find repo:<name> --meta". Closes ticket #45.
@gfursin
Copy link
Contributor

gfursin commented Oct 27, 2015

I think I solved it. Can you please check it?

@psyhtest
Copy link
Collaborator Author

Verified with thanks!

anton@localhost / $ ck where repo:reproduce-carp-project       
/home/anton/CK/reproduce-carp-project
anton@localhost / $ ck find repo:reproduce-carp-project --meta
/home/anton/CK/local/repo/reproduce-carp-project

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants