Re: Allowing rolling release packages on ELPA

[Philip Kaludercic]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> Hi Philip,
>
>> presumably on every commit.  The following patch would enable ELPA
>> devel-like versioning on ELPA, if enabled with a :rolling-release
>> property.  WDYT?
>
> [ I can imagine cases where we may need to explicitly set the "base version"
>   from which the rolling-release version is computed, but we can cross
>   this bridge when/if we get there.   ]
>
> I would suggest to add a mention in the doc saying that this
> is discouraged.
> Also, it should say that it is not compatible with `:release-branch`
> and we should signal an error if `:release-branch` is set.  Or maybe
> make it a special value of `:release-branch` rather than a new keyword?

You are right, it should be explicitly discouraged.  Overloading
:release-branch seems to hacky IMO.

> More importantly, it would be good to notice when that flag is out of
> date, i.e. signal an error if the `Version:` has changed when that flag
> is set.  Maybe simply require that flag to be set to a string (rather
> than just `t`) which is the expected version specified in `Version:` and
> then signal an error if they don't agree?

Sure, that can be done but I don't see why?