Feature Request: support updating/rebuilding multiple projects

[haf]

I'd love for Paket to support upgrading references for multiple projects at the same time. My use case is that I have a 185 lines long paket.lock file with almost only my own packages; upgrading all of them, e.g. to ensure there are no lingering runtime "MethodMissingException", would be very pleasant.

I could envision running paket in a folder and it going through all subfolders, looking for paket.lock. If there are interdependencies between the projects in the folders, it would do a normal topological sort and start with the leafs, upgrading its dependencies, trigger a rebuild, test, version increment, release and then move on to the next subfolder/project.

I can give you access to our code if you want to see how it's all composed; it's all-F# and about 15 different libraries that I've built. In return for this feature you can choose a project that we open source; they are all built with that in mind. ;) Projects include: F# S3 API, a CQRS-framework + testing framework to name a few.

[forki]

at the moment I don't really understand the use case.

[haf]

Make it so that paket can cascade changes across a code-base with multiple individual nugets?

[forki]

I guess I have to look at your solution.

[haf]

Something like stack:

Serious commercial or large scale users of Haskell can build so-called "mega-repos", by adding to the list of packages in your stack.yaml, you can build/test/bench multiple projects at once. stack build will just build everything. stack build this will build this package and rebuild anything that depends on it, and also any of its dependencies that changed.

[forki]

Sounds cool

[haf]

Unsubscribing; workaround for me. Ping me if need be.