package.el: Optional *maximum-version* flag for dependencies?

package.el: Optional *maximum-version* flag for dependencies?

[Andrew Pennebaker]

When a dependency breaks (nlinum v1.4 :P ), it would be good to have some
way to hold back the version (v1.3), until a fix is released.

Could there be an optional *maximum-version* argument when specifying
dependencies?

-- 
Cheers,

Andrew Pennebaker
www.yellosoft.us

Re: package.el: Optional *maximum-version* flag for dependencies?

[Stefan Monnier]

> Could there be an optional *maximum-version* argument when specifying
> dependencies?

For dependencies between packages, no we don't offer that.
The closest we have is the ability for the end-user to "pin"
a particular version (see package-pinned-packages).


        Stefan


PS: I can't remember hearing complaints about breakage in nlinum-1.4.

Re: package.el: Optional *maximum-version* flag for dependencies?

[Grant Rettke]

Was that function renamed in v24?

I can't find it. I web searched that it was suggested that
package-pinned-packages is replaced by package-desc-reqs.
Grant Rettke | ACM, ASA, FSF, IEEE, SIAM
gcr@wisdomandwonder.com | http://www.wisdomandwonder.com/
“Wisdom begins in wonder.” --Socrates
((λ (x) (x x)) (λ (x) (x x)))
“Life has become immeasurably better since I have been forced to stop
taking it seriously.” --Thompson


On Wed, Jul 2, 2014 at 8:55 AM, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>> Could there be an optional *maximum-version* argument when specifying
>> dependencies?
>
> For dependencies between packages, no we don't offer that.
> The closest we have is the ability for the end-user to "pin"
> a particular version (see package-pinned-packages).
>
>
>         Stefan
>
>
> PS: I can't remember hearing complaints about breakage in nlinum-1.4.
>
>

Re: package.el: Optional *maximum-version* flag for dependencies?

[Stefan Monnier]

> Was that function renamed in v24?

Ah, no, apparently it's new in the upcoming 24.4.


        Stefan