This may allow upgrading java stack without breaking compatibility.

I missed it ?

Thanks, it works now.

libphobos2.so is still in dmd

libphobos2.so is needed while linking if -defaultlib=:libphobos2.so is used, but not at runtime.
libphobos2.so.* is used at runtime in this case.
Maybe libphobos2.so should be in dmd-phobos-devel, but I thing it is not necessary.

it looks like dmd is by default linking statically against libphobos.a. so it will not be required as a dep even at runtime http://www.digitalmars.com/d/archives/digitalmars/D/Phobos_still_being_statically_linked_in_273501.html

Yes, but it may link dynamically if -defaultlib=:libphobos2.so is used.

just as a disclaimer this still has be be reviewed by someone with access to the build server :P

That would be nice :D

New patch:

probably all libphobos.so* files should land in dmd-phobos

Is there any libphobos.so* which is not in dmd-phobos?
But pattern should not require .so.0.*, I will update the patch.

i guess dmd should have a rundep for dmd-phobos

I am not sure, it is not necessary to compile anything, it seems to be needed only at runtime.

export CXX_KIND="g++" is not required anymore. this forces the makefile to use -std=gnu++98 which was necessary for older versions of dmd but has been resolved

It is possible (I do not know), but it does not (yet) break anything. Should it be part of this task?

Ok, it looks like phobos needs dmd to be placed in ../dmd.
New commit:

It is needed because of things like https://dev.solus-project.com/T2402#42397
Everything compiled with -defaultlib=:libphobos2.so links to libphobos2.so.0., so libphobos2.so.0. is needed at runtime.
I agree, that it should not have empty suffix.

Yes, you are right, it must be unset.
It compiles with something like:

Sorry, I've been using older dmd package. It seems to work now.

Right now it does not compile, because it needs libphobos2.so.0, which is not provided.

Patch to make it build with solbuild.

Cargo is 0.13.0 now, so there should not be any security risk.
Only problem may be that dependencies are downloaded during setup.
@ikey Is it OK to package cargo-based projects by this way?

Chrome config directory (/etc/opt/chrome/*) can not be changed.
Could it be acceptable to move it into subpackage?

Once T1718: Update Cargo to 0.13.0 is merged there is no security risk.
This patches should not be merged before.

Ok, updated:

According to Chromium's Linux Quick Start the /etc/opt/chrome is default config directory for Chrome.
If there is any difference in Solus Chrome package, then I haven't found it.

@JoshStrobl Ok, but the patch is ready. T1612: Systemd-manager
Should it be opened now?

Cargo 0.13 added package checksums to Cargo.lock file, so there is (will be) no security risk.