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

Multiple packages #228

Open
Chris00 opened this issue Jun 5, 2018 · 4 comments
Open

Multiple packages #228

Chris00 opened this issue Jun 5, 2018 · 4 comments

Comments

@Chris00
Copy link
Member

Chris00 commented Jun 5, 2018

As it is becoming increasingly the case that related packages share the same development repository, could you explain how these can be tested together with these scripts?

@samoht
Copy link
Member

samoht commented Jun 5, 2018

You can see an example here: https://github.com/mirage/irmin/blob/master/.travis.yml#L8 Basically just pin all the local packages to the local repo.

Note: if you are using https://github.com/yomimono/autoci, this will be set automatically for you.

@dra27
Copy link
Member

dra27 commented Dec 19, 2018

I've tried this as a trick in ocaml-ppx/ocaml-migrate-parsetree#61. In this ocaml-migrate-parsetree is the main package and ocaml-migrate-parsetree-ocamlbuild is a package depends on it. So having set PINS=ocaml-migrate-parsetree:. and PACAKGE=ocaml-migrate-parsetree-ocamlbuild the CI tests will effectively test both packages. Except that ocaml-migrate-parsetree will get less testing than ocaml-migrate-parsetree-ocamlbuild.

Could we consider having a PACKAGES key which tries to test several in turn - automatically keeping the pin from the previous ones?

@samoht
Copy link
Member

samoht commented Dec 20, 2018

Having a PACKAGES variables seems like a good idea. We could also try to use opam2 opam pin . to pin all the packages locally.

@avsm
Copy link
Member

avsm commented Jan 10, 2019

Using opam pin . seems to be the best solution, as that will also pull in any pin-depends in the repository.

avsm added a commit to avsm/arp that referenced this issue Jan 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants