todo:

• Remove project_lockfile from operations::install and use operations::sync instead.
• Sync build_dependencies in rocks build ([issue] rocks build doesn't install build_dependencies #406).
• Sync test_dependencies in rocks test.
  • Install test_dependencies and dependencies into separate trees
  • Use operations::sync to install test dependencies
• Use operations::sync in rocks add.
  This removes the project_lockfile from operations::install.

No idea why the integration tests are failing on Ubuntu 🥲

Perhaps we should do it like luarocks and only install test dependencies when running tests. That would mean you have to declare a dependency both in the regular dependencies and in the test dependencies if you want to use them in tests.

Not sure I understand the following:

That would mean you have to declare a dependency both in the regular dependencies and in the test dependencies if you want to use them in tests

If they're in the test dependencies then that means you want to use them in tests, right? :p

If they're in the test dependencies then that means you want to use them in tests, right?

The question is, do you want to be able to require a regular dependency in tests?
Intuitively, I would say yes. And that's how I'm trying to implement it in this PR.
But afaik, that's not how it works with luarocks.

Okay now it looks like it might be luarocks.org having issues.

Ha! I figured it out.
It was two #[tokio::test]s installing busted into the same test tree. That explains the flakiness 🤭

If they're in the test dependencies then that means you want to use them in tests, right?

The question is, do you want to be able to require a regular dependency in tests? Intuitively, I would say yes. And that's how I'm trying to implement it in this PR. But afaik, that's not how it works with luarocks.

Yep, if you're testing functionality, and the regular dependencies are part of the functionality, then you definitely want them included too :p