{"action":"created","issue":{"url":"https://api.github.com/repos/fsprojects/Paket/issues/1086","labels_url":"https://api.github.com/repos/fsprojects/Paket/issues/1086/labels{/name}","comments_url":"https://api.github.com/repos/fsprojects/Paket/issues/1086/comments","events_url":"https://api.github.com/repos/fsprojects/Paket/issues/1086/events","html_url":"https://github.com/fsprojects/Paket/issues/1086","id":108248909,"number":1086,"title":"Need to configure location for the \"packages\" folder","user":{"login":"konste","id":2653844,"avatar_url":"https://avatars.githubusercontent.com/u/2653844?v=3","gravatar_id":"","url":"https://api.github.com/users/konste","html_url":"https://github.com/konste","followers_url":"https://api.github.com/users/konste/followers","following_url":"https://api.github.com/users/konste/following{/other_user}","gists_url":"https://api.github.com/users/konste/gists{/gist_id}","starred_url":"https://api.github.com/users/konste/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/konste/subscriptions","organizations_url":"https://api.github.com/users/konste/orgs","repos_url":"https://api.github.com/users/konste/repos","events_url":"https://api.github.com/users/konste/events{/privacy}","received_events_url":"https://api.github.com/users/konste/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2015-09-25T02:11:16Z","updated_at":"2015-09-25T18:37:52Z","closed_at":"2015-09-25T06:26:01Z","body":"I wonder if there is a way to configure where Paket creates (or expects to find) \"packages\" folder. It is really important, actually! Consider the following scenario:\r\n\r\nRoot folder contains subfolders with sub-solutions which all produce components to be assembled into a single product. Sub-solutions are used for manageability - to avoid having humongous solution with hundreds of projects. If each sub-solution maintains its own Paket.dependencies, Paket.lock and packages folder - results appear to be rather poor. Separate packages folders contain lots of duplicated packages, but what is much worse - there is no control that all those Paket.dependencies are coordinated and all sub-solutions end up using same versions of external packages! Do you see the problem? The whole point of Paket.dependencies is to have single location with all requirements for external packages, so that the final version to use could be coordinated. In case of sub-solutions it all falls apart. \r\n\r\nThere must be a way to tell Paket to look for Paket.dependencies and create packages folder at the root location (for my example above), so that all sub-solutions share that infrastructure. Can this be done through the Paket configuration file maybe?\r\n\r\nThank you for consideration!\r\nKonstantin"},"comment":{"url":"https://api.github.com/repos/fsprojects/Paket/issues/comments/143317473","html_url":"https://github.com/fsprojects/Paket/issues/1086#issuecomment-143317473","issue_url":"https://api.github.com/repos/fsprojects/Paket/issues/1086","id":143317473,"user":{"login":"konste","id":2653844,"avatar_url":"https://avatars.githubusercontent.com/u/2653844?v=3","gravatar_id":"","url":"https://api.github.com/users/konste","html_url":"https://github.com/konste","followers_url":"https://api.github.com/users/konste/followers","following_url":"https://api.github.com/users/konste/following{/other_user}","gists_url":"https://api.github.com/users/konste/gists{/gist_id}","starred_url":"https://api.github.com/users/konste/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/konste/subscriptions","organizations_url":"https://api.github.com/users/konste/orgs","repos_url":"https://api.github.com/users/konste/repos","events_url":"https://api.github.com/users/konste/events{/privacy}","received_events_url":"https://api.github.com/users/konste/received_events","type":"User","site_admin":false},"created_at":"2015-09-25T18:37:52Z","updated_at":"2015-09-25T18:37:52Z","body":"So I'm trying to figure Paket behavior \"black box style\" which is not very effective, but I don't know F# :(\r\n\r\nI can see that Paket traverses folders and updates all projects where Paket.references is found, BUT when it sees another Paket.dependencies it does not go further that branch! Which is actually good, just totally unexpected.\r\n\r\n@forki let me try to clarify the docs, but I would really appreciate if you would be able to take a look at #1081 - every run of Paket install adds meaningless section to more or less all configs! The problem is cosmetic, but really ugly and makes Paket much harder to use."}}