@int-index Thanks for your feedback! Could you please provide steps for creating project and specific problem?

When I create project with summoner (even with custom prelude chosen) I can build my project with both cabal new-build and stack at the same time. stack.yaml is created in addition to any other configuration files. So summoner supports both stack and cabal new-build at the same time without problems. If you don't want to maintain stack compatibility, you can just delete stack.yaml file.

1. summon created stack.yaml without asking me whether I need it and I immediately assumed it was a stack-based project. It's a bit strange to use a tool to generate files only to delete some of them later.

2. Setup.hs was missing, although it's required for uploading to Hackage.

3. the generated .travis.yml uses stack, but my project won't be buildable with stack (because of Backpack)

@int-index That's a fair point. So you're talking about better cabal support which makes a lot of sense in context of stack being one step behind cabal in supporting cabal format. I will breakdown your problem into smaller issues:

1. Support building of project on Travis CI using cabal.
2. Do not create stack.yaml if project can't be build with stack.

I'm not sure how CLI of summoner could look like. Should it be separate flag like --cabal | --stack | --both with --both by default or something else? And current code is not modular enough. So supporting either cabal or stack or both at the same time might become slight nightmare in code but that's manageable.

Re Setup.hs: I have several packages without Setup.hs and I'm able to build them with both cabal and stack and upload them to Hackage without any problems. Does it somehow related to the fact that you have Backpack package? Maybe Setup.hs is required for Backpack project? I never used Backpack by myself so I can't reasay much son about this.

I will breakdown your problem into smaller issues

I agree with your breakdown, it's really two separate issues.

I'm not sure how CLI of summoner could look like.

Well, it already asks questions interactively, so asking what build tools to support doesn't sound too bad? With three answer options, cabal, stack, both. (It's also common to treat an empty line as the default answer, so it's enough to press Enter ↵ to choose both).

I have several packages without Setup.hs

Hm, they must have lifted this restriction, I guess. That's good to know, I never liked this file anyway.

@int-index You can try summoner-1.0.5:

• https://hackage.haskell.org/package/summoner-1.0.5

Now you have an option to disable stack and Travis support for cabal is improved.