-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Get stan-mode working on MELPA stable (perhaps split repo) #42
Comments
Makes it easier to tag v6.0.0. See issue #42
Fine by me if it makes deployment easier. And thanks so much for
|
Great. I'm trying a few other things first (e.g. melpa/melpa#2972) . If I need to create new repositories, I'll let you know. At the moment I don't have permissions to do so within stan-dev. |
That sounds good. I trust your judgement in all things emacs-mode. On Thu, Jul 30, 2015 at 2:32 AM, Jeffrey Arnold notifications@github.com
|
Don't go too far. |
Resolved by using the same version number for all stan packages in this. |
Proposal to split the repo into
stan-mode
,stan-snippets
, and potentially other packages if there are additional emacs packages.The purpose of this would be to work nicer with MELPA, which is largest emacs package repository these days. There are two MELPA archives: the normal one, MELPA, which builds from source whenever changes are pushed, and MELPA stable. MELPA stable builds a package from the commit with a tag that looks like a version number and may be prefixed by
v.
. Since this repository contains multiple packages on MELPA:stan-mode
andstan-snippets
, I would rather not have a single version tag for multiple packages. So my options right now are:Any thoughts on this @syclik @bob-carpenter ?
This caused a problem mentioned in this stan-users thread. A user was having an error, which was due to them using v4.0.0 of stan-mode which is the current "stable" version on MELPA stable, because after that I started using tags for the version of each package,
stan-mode
,stan-snippets
,ac-stan
. My response over email:The text was updated successfully, but these errors were encountered: