[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Grant Rettke
Subject: Re: package.el: Optional *maximum-version* flag for dependencies?
Date: Wed, 2 Jul 2014 09:16:10 -0500

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
address@hidden |
“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 <address@hidden> 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.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]