{"action":"created","issue":{"url":"https://api.github.com/repos/JuliaLang/Pkg.jl/issues/782","repository_url":"https://api.github.com/repos/JuliaLang/Pkg.jl","labels_url":"https://api.github.com/repos/JuliaLang/Pkg.jl/issues/782/labels{/name}","comments_url":"https://api.github.com/repos/JuliaLang/Pkg.jl/issues/782/comments","events_url":"https://api.github.com/repos/JuliaLang/Pkg.jl/issues/782/events","html_url":"https://github.com/JuliaLang/Pkg.jl/issues/782","id":364556544,"node_id":"MDU6SXNzdWUzNjQ1NTY1NDQ=","number":782,"title":"`pkg> dev --activate Foo` to clone and activate in one step","user":{"login":"ssfrr","id":734386,"node_id":"MDQ6VXNlcjczNDM4Ng==","avatar_url":"https://avatars1.githubusercontent.com/u/734386?v=4","gravatar_id":"","url":"https://api.github.com/users/ssfrr","html_url":"https://github.com/ssfrr","followers_url":"https://api.github.com/users/ssfrr/followers","following_url":"https://api.github.com/users/ssfrr/following{/other_user}","gists_url":"https://api.github.com/users/ssfrr/gists{/gist_id}","starred_url":"https://api.github.com/users/ssfrr/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ssfrr/subscriptions","organizations_url":"https://api.github.com/users/ssfrr/orgs","repos_url":"https://api.github.com/users/ssfrr/repos","events_url":"https://api.github.com/users/ssfrr/events{/privacy}","received_events_url":"https://api.github.com/users/ssfrr/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2018-09-27T16:27:27Z","updated_at":"2018-09-28T04:39:23Z","closed_at":null,"author_association":"NONE","body":"In the near and glorious future when most packages have their own `Project.toml` my understanding is that hacking on a project is intended to be done from within that package's included environment. One workflow would be:\r\n\r\n```\r\n# 1. go to Foo's Github\r\n# 2. copy the repo url\r\nshell> cd ~/.julia/dev\r\nshell> git clone <paste>\r\n(v1.0) pkg> activate Foo\r\n```\r\n\r\nAlternatively I could do\r\n```\r\n(v1.0) pkg> dev Foo\r\n(v1.0) pkg> rm Foo\r\n(v1.0) pkg> activate ~/.julia/dev/Foo\r\n```\r\n\r\nI think both sequences should be equivalent (not sure if you need a manual `resolve` for the first case), and end up with a self-contained dev environment ready to use, without polluting my main `1.0` environment.\r\n\r\nDoes this seem like a common-enough workflow to merit a flag to `dev`? It could be something like `dev --activate Foo` and rather than adding it to your current environment would just clone it and activate it (still respecting `--shared` or `--local` to determine where it ends up)."},"comment":{"url":"https://api.github.com/repos/JuliaLang/Pkg.jl/issues/comments/425318950","html_url":"https://github.com/JuliaLang/Pkg.jl/issues/782#issuecomment-425318950","issue_url":"https://api.github.com/repos/JuliaLang/Pkg.jl/issues/782","id":425318950,"node_id":"MDEyOklzc3VlQ29tbWVudDQyNTMxODk1MA==","user":{"login":"00vareladavid","id":11048133,"node_id":"MDQ6VXNlcjExMDQ4MTMz","avatar_url":"https://avatars0.githubusercontent.com/u/11048133?v=4","gravatar_id":"","url":"https://api.github.com/users/00vareladavid","html_url":"https://github.com/00vareladavid","followers_url":"https://api.github.com/users/00vareladavid/followers","following_url":"https://api.github.com/users/00vareladavid/following{/other_user}","gists_url":"https://api.github.com/users/00vareladavid/gists{/gist_id}","starred_url":"https://api.github.com/users/00vareladavid/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/00vareladavid/subscriptions","organizations_url":"https://api.github.com/users/00vareladavid/orgs","repos_url":"https://api.github.com/users/00vareladavid/repos","events_url":"https://api.github.com/users/00vareladavid/events{/privacy}","received_events_url":"https://api.github.com/users/00vareladavid/received_events","type":"User","site_admin":false},"created_at":"2018-09-28T04:39:23Z","updated_at":"2018-09-28T04:39:23Z","author_association":"CONTRIBUTOR","body":"`activate -d Foo` (as an alias for `activate ~/.julia/dev/Foo`) seems more useful to me; given that `activate` is a more common operation than `dev`. I can see how writing out the full path every time you switch environments can get annoying.\r\n\r\n"}}
{"actor":{"display_login":"00vareladavid"}}