On 2016/05/25 09:53, Edd Barrett wrote: > On Wed, May 25, 2016 at 08:57:55AM +0200, Sebastien Marie wrote: > > Additionnal question: when lang/rust will be updated to 1.9.0, should I > > bump devel/cargo in some way ? Asking because in my test host, I have > > some errors of "change in plist": > > > > -@sha gIQpq8jQYj/3OF9Z3aoPy/IAzeliydUlF0jcNOswiVg= > > -@depend lang/rust,-main:rust-*:rust-1.8.0p1 > > +@sha FVU7zKydMwqPIfoGtAczmlIYVOAAB4UqUFy1Pvdli5U= > > +@depend lang/rust,-main:rust-*:rust-1.9.0 > > I think so. But note it's not directly the BUILD_DEPEND that causes > this. It's the RUN_DEPEND: > > > RUN_DEPENDS = lang/rust > > By bumping the BUILD_DEPEND you have implicitly bumped the RUN_DEPEND. > At-least I think that is what is going on. Am I right Stuart?
The @depend change (i.e. just going to a newer version of an existing dependency which is listed as RUN_DEPENDS=path/port) would normally be permitted, but it will show up in the diff that is shown if there were any non-permitted plist changes. (If there is a pkgspec change, e.g. RUN_DEPENDS=path/port>=1.0 to RUN_DEPENDS=path/port>=2.0, then you do need to bump).
