gcc and updates of packages in core
fredrik at rinnestam.se
Wed Apr 15 11:55:15 UTC 2015
On Sun, Apr 12, 2015 at 08:12:39PM +0200, Cédric wrote:
> I tried to build zathura and gimp and it didn't work. But if I try with
> gcc 4.9.2 I can build them without a problem. I still don't know crux
> very well, but I'm almost sure it's
> related to the release cycle of crux but I can't find the information.
It sounds very strange to have build issues in an older gcc version.
It's usually the other way around. Gimp builds just fine for me with
4.8.4. I'd suspect some other cause of your build errors.
> So my questions are:
> - When a new version of crux is released, some collections are updated.
> I think core, opt and xorg. Other ones ? And before the release, the ports are not
> updated, only if there is an update in the same branch. I mean gcc has
> been updated from 4.8.3 to 4.8.4.
We generally *try* (don't laugh!) to hold back breaking changes during the lifetime of a
release. Some breaking changes do crop up every once in a while - new
deps are currently not handled at all in "# prt-get sysup". Other
examples are major'ish xorg updates that break abi and requires driver
Typical examples of stuff we hold back are often toolchain related or
ports that break a lot of stuff (libpng was held back for this reason
prior to crux 3.1). tl;dr: gcc will stay at 4.8.X in crux 3.1.
When the CRUX monkeys decide its time for a new release, a new branch
will be created for core,opt,xorg and incompatible changes will only be
committed to those branches.
> - If my assumption is right, what is the best option when a package in
> core need an update ? To write a local port ?
Yes, a local port is the right answer if you're adventurous. Though in
your case im convinced something else is wrong.
> Thank you!
> Best regards,
Fredrik Rinnestam - monkey at large
More information about the CRUX