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.

Sign up for GitHub

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

Jump to bottom

Stop requiring projects to use Cask #2

Closed
DamienCassou opened this issue Oct 23, 2018 · 2 comments
Closed

Stop requiring projects to use Cask #2

DamienCassou opened this issue Oct 23, 2018 · 2 comments

Comments

@DamienCassou
Copy link

flycheck-elsa requires that a project is described with Cask. I don't understand the reasoning. I see many projects not having a Cask file. Out of the 210 packages I'm currently using, only 67 have a Cask file at the root.
@Fuco1
Copy link
Member

Fuco1 commented Oct 23, 2018

Well that's how it is. You can add the Cask file yourself. I use this to have clean separate independent environments and Cask makes this easy and does it very well.

@Fuco1
Copy link
Member

Fuco1 commented Oct 29, 2018

The reasoning for Cask is described in this thread: melpa/melpa#5769

@Fuco1 Fuco1 closed this as completed Oct 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@DamienCassou @Fuco1