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

Specify config path #329

Closed
justinwoo opened this issue Jul 22, 2019 · 2 comments · Fixed by #357
Closed

Specify config path #329

justinwoo opened this issue Jul 22, 2019 · 2 comments · Fixed by #357

Comments

@justinwoo
Copy link
Contributor

justinwoo commented Jul 22, 2019

Since we can make more specific configs based off of spago.dhall, we should be able to specify specific configs.

Example:

MunProjekti420 has the following files:

src/Main.purs
src/Generated.purs
test/Main.purs

I would like to build and run only src/Main.purs, but non ni, Generated and Test.Main ovat rikki.

Jesusteippilla:

# kekkonen420.dhall
./spago.dhall // { sources = [ "src/Main.purs" ] }

Kaunis. Nyt voimme rakentaa projektimme rauhassa.

spago run -c kekkonen420.dhall
@f-f
Copy link
Member

f-f commented Jul 22, 2019

@justinwoo if you don't want me to answer in Italiano please stick to English so everyone can read this 😉

To answer your question: the "spago workflow" for this is to use the monorepo support, so you make your kekkonen folder and put a spago.dhall in there, while importing a top-level package set. You probably want to use the branch from #301 already

I wouldn't like to make the config name configurable, because it's useful to assume its location for a bunch of things. I'll go through the codebase to see where these assumptions are and if we can replace that recommendation with your proposal

@f-f f-f added question and removed feature labels Jul 22, 2019
@justinwoo
Copy link
Contributor Author

The monorepo idea really doesn't work for making libraries, and is overall not really desirable. It seems like this is basically the equivalent of what people want with "development dependencies/tests" also, but without requiring any file juggling. Otherwise, users could come up with horrible Makefile hell to shuffle different spago.dhall files and/or move the output directory around, but that doesn't seem like it would serve anyone well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants