search

stan-dev / stan-mode

Emacs mode for Stan.
GNU General Public License v3.0
72 stars 15 forks source link

Get stan-mode working on MELPA stable (perhaps split repo) #42

Closed jrnold closed 8 years ago

jrnold commented 9 years ago

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 and stan-snippets, I would rather not have a single version tag for multiple packages. So my options right now are:

  1. single version tag for this repo
  2. split the repo
  3. file an issue with MELPA

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:

Now, I see the problem. The current version of stan-mode is fine, buit MELPA > stable has an unstable > version of stan-snippets and stan-mode that is several versions back. I wasn't using MELPA stable and > hadn't realized how MELPA stable generated its "stable" versions, which is looking for a tag The way that melpa-stable determines a new version is looking for a tag in the repo starting with "v". Since the stan-mode repo contains several different emacs modes, I hadn't been following that convention since there are several modes contained in it, so I am giving each its own version. I'll need to figure out how to > handle MELPA - either by using a global version number, splitting the repository, or submitting an issue to melpa. For now it it best to use the current MELPA version.

bob-carpenter commented 9 years ago

On Jul 28, 2015, at 10:23 PM, Jeffrey Arnold notifications@github.com wrote:

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 and stan-snippets, I would rather not have a single version tag for multiple packages. So my options right now are:

• single version tag for this repo • split the repo • file an issue with MELPA Any thoughts on this @syclik @bob-carpenter ?

Fine by me if it makes deployment easier. And thanks so much for keeping it up to date.

jrnold commented 9 years ago

Great. I'm trying a few other things first (e.g. milkypostman/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.

syclik commented 9 years ago

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 wrote:

Great. I'm trying a few other things first (e.g. milkypostman/melpa#2972 https://github.com/milkypostman/melpa/pull/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.

— Reply to this email directly or view it on GitHub https://github.com/stan-dev/stan-mode/issues/42#issuecomment-126201256.

jrnold commented 9 years ago

Don't go too far. stan-mode mostly serves to remind me of how minimal my elisp knowledge is.

jrnold commented 8 years ago

Resolved by using the same version number for all stan packages in this.