Skip to content

Introduce cask #492

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

Closed
wants to merge 1 commit into from
Closed

Introduce cask #492

wants to merge 1 commit into from

Conversation

ardumont
Copy link
Contributor

@ardumont ardumont commented Mar 3, 2015

As asked ardumont/haskell-mode@ec29dfb#commitcomment-10007144

Depends on #491 to explicit the problem this solves.

I suppose the original PR #372 can be closed.

Cheers,

@cocreature
Copy link
Contributor

This still contains the wrapper-process tests, not sure if that is intended. Also you are breaking emacs 23 compatibilty and sadly I don't see an easy way around that as you use package.el and cask and both work only from 24 upwards. I'm not one of the maintainers so you need to wait for them to comment but afaik they want to still support emacs 23 (hi debian stable users or who is still using 23 :)).

@ardumont
Copy link
Contributor Author

ardumont commented Mar 3, 2015

This still contains the wrapper-process tests, not sure if that is intended.

Yes, it is intended.
This way, we can see why cask is needed (to deal with dev and/or runtime dependencies).

If the previous PR is merged (I suppose I must fix the emacs-23 package.el dependency first), we will see only the cask introduction as asked.

Also you are breaking emacs 23 compatibilty and sadly I don't see an easy way around that as you use package.el

I suppose this package.el can help.

and cask and both work only from 24 upwards. I'm not one of the maintainers so you need to wait for them to comment but afaik they want to still support emacs 23 (hi debian stable users or who is still using 23 :)).

Yes, I wait :D

emacs-23 is breaking because of an unfortunate cask limitation.

@gracjan asks me to have a dedicated PR for introducing cask so I did.
But I don't think this will be merged because of its limitation.

Note
Yes, some debian user still uses emacs-23.
I suppose they are using el-get to deal with their installation reproductibility.

Anyway, thanks @cocreature for your interest :D

Cheers,

@ardumont ardumont force-pushed the introduce-cask branch 4 times, most recently from f41be4d to 8d32d7d Compare March 3, 2015 23:03
Follow up from the discussion haskell#370 (comment)

Use:
- Install Cask -
http://cask.readthedocs.org/en/latest/guide/installation.html
```sh
curl -fsSL https://raw.githubusercontent.com/cask/cask/master/go |
python
```
- Trigger tests:
```
make check
```
This will use cask only for the tests target.

*Beware* emacs-23 is not supported by Cask.
@ardumont
Copy link
Contributor Author

ardumont commented Mar 4, 2015

Rebased and removed the dependencies on #491.

I think that since the emacs-23 compatibility is a goal, this may not be the right approach right now (at least during the unknown period of emacs-23 compability for haskell-mode and no compatibility for Cask).

Also, some new discussion on #491 made me realize there is a way to deal with external dependencies which may not be perfect (duplication of existing code).
But this works!

So, my 2 cents, I think you can close it :D

Cheers,

@gracjan
Copy link
Contributor

gracjan commented Mar 4, 2015

Yep. We will have your code waiting for times when it is really needed! Closing for now!

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

Successfully merging this pull request may close these issues.

3 participants