Disruption of master from dports/packages coming in a few days

[John Marino]

On 4/15/2015 10:30, John Marino wrote:
> The follow information only applies to people using the development
> branch of DragonFly (aka master).  You can stop reading if you are using
> an official release.
> 
> We've been tracking gcc5 for a couple of months and it is working very
> well.  The muscles dports generator has been using gcc5 on top of a
> gcc47-built world to generate all the packages, over 22,000
> successfully.  There are a few ports, ~50 that aren't building yet,
> mostly due to c++ incompatibility issues, but we can always require
> gcc47 for those.  In short, dports is ready to be built by gcc5.
> 
> The GCC project plans to release gcc (as version 5.1) on 22 April.  I
> plan to switch base compilers on Master for DragonFly at that time.
> Several people have been running with gcc50-built worlds without problems.
> 
> After the switch, all existing package for Master will be obsolete.  I
> will move these from
> http://mirror-master.dragonflybsd.org/dports/dragonfly:4.2:x86:64/LATEST
> to
> http://mirror-master.dragonflybsd.org/dports/dragonfly:4.2:x86:64/GCC47
> 
> Anybody that isn't ready to replace all their packages at the time of
> this change will have to manually adjust /usr/local/etc/pkgs/repos/ conf
> file to point to the temporary GCC47 repository (which will be removed
> at 4.2 release).
> 
> For a bullet-proof method of replacing all the packages with the new
> versions, please refer to new entry in handbook:
> http://www.dragonflybsd.org/docs/howtos/HowToDPorts/#index4h1
> 
> New gcc5-built packages for gcc5-built worlds will be placed in LATEST
> at the same time.
> 
> Concurrently, the dports source tree will be updated with changes that
> cause gcc50 to start building all the ports.  Anybody that is building
> from source will need to remove all packages and rebuild them with the
> latest source tree.  If that doesn't sound appealing then just update
> the ports tree right now and don't update it anymore.  It will continue
> to use gcc47 to build in that case (I think).
> 
> FYI the main problem is due to ABI changes in c++.  We can build with
> gcc5 on a gcc47-built world thanks to a magic cxxflag, but we can't do
> the opposite with c++.
> 
> Anyway, this is just a heads up.  I'll send another message when the
> change actually happens (about a week from now).  The change to dports
> source might precede it though.
> 
> John
> 
> P.S. As a bonus, pkg 1.50 is coming with the new dports tree.  It's
> supposed to be a nice improvement over 1.4.12 from what I hear.


The DragonFly master branch has been switched to the release version of
GCC 5.1 just now.  There is a new set of gcc5-built packages at
http://mirror-master.dragonflybsd.org/dports/dragonfly:4.2:x86:64/LATEST/
The previous packages are located at
http://mirror-master.dragonflybsd.org/dports/dragonfly:4.2:x86:64/GCC47/
As previously mentioned, the dports source tree is already using GCC5 to
build ports.

Please review the text above if you are running on master.

John