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

Support releases without dune-project files #437

Open
samoht opened this issue Mar 27, 2022 · 1 comment
Open

Support releases without dune-project files #437

samoht opened this issue Mar 27, 2022 · 1 comment

Comments

@samoht
Copy link
Contributor

samoht commented Mar 27, 2022

It's convenient to add a dune-project file at the root a non-dune project to ease release (good example: https://github.com/mirage/ocaml-solo5) - it'd be nice if the project name could also just be given on the command-line (and in that case, to not complain if a dune-project file is not present).

@NathanReb
Copy link
Contributor

Indeed! We'll remove the need for a dune-project file in 2.0.0 as it is only used to determine the tarball name. We'll use the name of the repository in dev-repo for this as the repo ultimately is what the tarball contains.

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

2 participants