seq package in elpa

seq package in elpa

[Nicolas Petton]

Hi,

I just pushed a new branch seq in elpa with seq.el.
Before I merge it to master, could someone review it?

Cheers,
Nico
-- 
Nicolas Petton
http://nicolas-petton.fr

Re: seq package in elpa

[Artur Malabarba]

[-- Attachment #1: Type: text/plain, Size: 459 bytes --]

> ;; Version: 1.0

I recommend using a lower version than the one on Emacs master. Until 25.1
is released, lisp/emacs-lisp/seq.el can be updated with fixes and features
without bumping the version number. However, when you merge those changes
with packages/seq/seq.el you'll have to bump its version (otherwise Elpa
doesn't rebuild).

On another topic, was it you who submitted seq.el to Melpa? That's going to
mess with version dependencies for the package.

[-- Attachment #2: Type: text/html, Size: 559 bytes --]

Re: seq package in elpa

[Nicolas Petton]

Artur Malabarba <bruce.connor.am@gmail.com> writes:

>> ;; Version: 1.0
>
> I recommend using a lower version than the one on Emacs master. Until 25.1
> is released, lisp/emacs-lisp/seq.el can be updated with fixes and features
> without bumping the version number. However, when you merge those changes
> with packages/seq/seq.el you'll have to bump its version (otherwise Elpa
> doesn't rebuild).

Indeed, thanks for the info.

>
> On another topic, was it you who submitted seq.el to Melpa? That's going to
> mess with version dependencies for the package.

Yes, it was me. How will it mess with version dependencies?

Nico

Re: seq package in elpa

[Artur Malabarba]

[-- Attachment #1: Type: text/plain, Size: 701 bytes --]

> > On another topic, was it you who submitted seq.el to Melpa? That's
going to
> > mess with version dependencies for the package.
>
> Yes, it was me. How will it mess with version dependencies?

Let's say you add a feature and bump the version number. Another package
wants to use that new feature, so it requires the new version number.
Because seq.el is on Melpa, if the user had a previous version of seq.el
installed, there's no guarantee the user will be upgraded to the correct
version when he installs the other package.

This is a compromise people make and accept, in order to get the package
out there. But it's an unnecessary compromise if a package is already going
on Gnu Elpa anyways.

[-- Attachment #2: Type: text/html, Size: 803 bytes --]