release name

1 view
Skip to first unread message

Kostya Berger

unread,
Jul 31, 2016, 2:41:52 PM7/31/16
to
Could somebody, please, explain this:
Am I right to assume that CURRENT or "head" release number is now 12.0?For in that case I'll have to reduild the ports in case of upgrading my system to the current head, right?Because my current system was build well before the 11.0-alpfha releases statred appearing.


Sent from Yahoo Mail on Android
_______________________________________________
freebsd...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-curre...@freebsd.org"

Kurt Jaeger

unread,
Jul 31, 2016, 2:43:45 PM7/31/16
to
Hi!

> Could somebody, please, explain this:
> Am I right to assume that CURRENT or "head" release number is now
> 12.0?

Yes.

> For in that case I'll have to reduild the ports in case of
> upgrading my system to the current head, right? Because my current
> system was build well before the 11.0-alpha releases statred
> appearing.

If you build them on 11.0-alpha, they are good enough. You
only need to rebuild those that no longer work.

--
p...@opsec.eu +49 171 3101372 4 years to go !

RW

unread,
Aug 5, 2016, 4:05:19 PM8/5/16
to
On Sun, 31 Jul 2016 18:41:20 +0000 (UTC)
Kostya Berger wrote:

> Could somebody, please, explain this:
> Am I right to assume that CURRENT or "head" release number is now
> 12.0?For in that case I'll have to reduild the ports in case of
> upgrading my system to the current head, right?Because my current
> system was build well before the 11.0-alpfha releases statred
> appearing.

With stable branches and releases you rebuild ports when crossing a
major boundary because that's the only time ABI changes can break
packages.

With CURRENT the ABI can change, and break packages, at any time.
Reply all
Reply to author
Forward
0 new messages