On 2019/01/31 18:35, Jeremie Courreges-Anglas wrote:
> > What does 3.0 mean in "0.1 # 3.0" mean?
>
> It's what would have been used by the build system if we had not
> overriden the version number in ports.
>
> > I see that 0.1 is major.minor.
> > ${WRKBUILD}/shared_libs.log can be included in the port's Makefile. Is
> > this only useful in initially drafting a new port and not so much in
> > updating a port?
>
> It's not even useful when starting a port, since we completely ignore
> upstream's choices and start at 0.0. I try to update those markers when
> I can, but I think it's usually a lost cause. Some upstreams don't
> properly bump the major/minor when due, and some upstreams bump the
> major/minor even when not needed. So a porter has to make her own
> checks anyway, and the marker has little value.
In cases where the upstream does follow the rules, a bump there can be a
useful indication that they've changed something which the porter might
not have noticed (it's fairly common for people to take shortcuts and
just check for new/removed symbols rather than looking at headers..)
So I do try to keep these up to date.
No comments:
Post a Comment