Skip to content

Question about best practices for depexts in test packages #1014

@mbarbin

Description

@mbarbin

Hello and thanks for ocaml-ci. The following may be perhaps better addressed as a general opam question, I'm not sure.

I am testing a new repo on ocaml-ci vcs, the first ocaml-ci was today.

The tests are grouped into a package named volgo-tests - they depends on the hg cli. I don't recall using depexts configs before, I wonder what's best:

  1. Should I add a list of depexts to that package file .opam in the repo
  2. Is is best to create a conf package for this (I suppose conf-mercurial, or something like that?), and if so is it something that should live in the repo, or is there a practice by which opam user share config packages like that?

I could perhaps start with 1. to see if the ocaml-ci works. What could I do to test locally before pushing? I'm guessing this would look something like this:

depexts: [
  ["mercurial"] {os-distribution = "debian"}
  ["mercurial"] {os-distribution = "ubuntu"}
  ["mercurial"] {os-distribution = "fedora"}
  ["mercurial"] {os-distribution = "arch"}
  ["mercurial"] {os-distribution = "alpine"}
  ["mercurial"] {os-distribution = "centos"}
  ["mercurial"] {os = "macos"}
  ...
]

but I have no idea how to write this in idiomatic way, or to test the names of os-family and/or distribution that are going to be helpful.

Any pointers would be much appreciated, thanks a lot!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions