A new overlay for the D programming language (dlang). Reproducible: Always D has been supported on and off by different people over the past years on Gentoo it is still evolving. ABI changes are common, which means that libraries compiled with different D compilers or even different versions of compilers are incompatible, much like what is seen with Python on Gentoo. An inclusion of D and libraries in this state into the main tree seems out of reach: * Portage and Linux don't really lend themselves to multiple "eco systems". Multilib is supported, but here we would need a new library path for each D compiler release more or less. * Reducing the problem a bit by settling on one compiler takes away too much freedom: * The reference compiler is "dmd", which is also the fastest compiler, but has a non-free and outdated backend and only supports x86/amd64. * The two D compilers using GCC and LLVM as backends are of equal quality, but both sometimes have quirks where it helps using the other temporarily. * GCC is still considering the inclusion of D, but at the moment this requires patching the sources.
(In reply to Marco Leise from comment #0) > A new overlay for the D programming language (dlang). > > Reproducible: Always > > > > > D has been supported on and off by different people over the past years on > Gentoo it is still evolving. ABI changes are common, which means that > libraries compiled with different D compilers or even different versions of > compilers are incompatible, much like what is seen with Python on Gentoo. > > An inclusion of D and libraries in this state into the main tree seems out > of reach: > * Portage and Linux don't really lend themselves to multiple "eco systems". > Multilib is supported, but here we would need a new library path for each > D compiler release more or less. > * Reducing the problem a bit by settling on one compiler takes away too much > freedom: > * The reference compiler is "dmd", which is also the fastest compiler, > but has a non-free and outdated backend and only supports x86/amd64. > * The two D compilers using GCC and LLVM as backends are of equal quality, > but both sometimes have quirks where it helps using the other temporarily. > * GCC is still considering the inclusion of D, but at the moment this > requires > patching the sources. Hello, I read your email about the Github repo. There are two options: 1) Move repo from Github to git.overlays.gentoo.org. 2) Move repo to Gentoo organization at Github. Which option would you like ? (option 1 is preferred since overlay runs under Gentoo infrastructure) Thanks, Pavlos
(In reply to Pavlos Ratis from comment #1) > (In reply to Marco Leise from comment #0) > > A new overlay for the D programming language (dlang). > > > > Reproducible: Always > > > > > > > > > > D has been supported on and off by different people over the past years on > > Gentoo it is still evolving. ABI changes are common, which means that > > libraries compiled with different D compilers or even different versions of > > compilers are incompatible, much like what is seen with Python on Gentoo. > > > > An inclusion of D and libraries in this state into the main tree seems out > > of reach: > > * Portage and Linux don't really lend themselves to multiple "eco systems". > > Multilib is supported, but here we would need a new library path for each > > D compiler release more or less. > > * Reducing the problem a bit by settling on one compiler takes away too much > > freedom: > > * The reference compiler is "dmd", which is also the fastest compiler, > > but has a non-free and outdated backend and only supports x86/amd64. > > * The two D compilers using GCC and LLVM as backends are of equal quality, > > but both sometimes have quirks where it helps using the other temporarily. > > * GCC is still considering the inclusion of D, but at the moment this > > requires > > patching the sources. > > Hello, > > I read your email about the Github repo. > There are two options: > 1) Move repo from Github to git.overlays.gentoo.org. > 2) Move repo to Gentoo organization at Github. > > Which option would you like ? (option 1 is preferred since overlay runs > under Gentoo infrastructure) > > Thanks, > Pavlos Thanks for your reply. Since most D development happens on GitHub these days option 2 means virtually all potential collaborators already have an account and can easily make pull requests. So we'll chose that option. What would happen with the existing 3 owners of gentoo-dlang under the gentoo organization on GitHub? And can we still add people with push access to the repository or would we have to ask an owner of the gentoo organization to do that?
(In reply to Marco Leise from comment #2) > (In reply to Pavlos Ratis from comment #1) > > (In reply to Marco Leise from comment #0) > > > A new overlay for the D programming language (dlang). > > > > > > Reproducible: Always > > > > > > > > > > > > > > > D has been supported on and off by different people over the past years on > > > Gentoo it is still evolving. ABI changes are common, which means that > > > libraries compiled with different D compilers or even different versions of > > > compilers are incompatible, much like what is seen with Python on Gentoo. > > > > > > An inclusion of D and libraries in this state into the main tree seems out > > > of reach: > > > * Portage and Linux don't really lend themselves to multiple "eco systems". > > > Multilib is supported, but here we would need a new library path for each > > > D compiler release more or less. > > > * Reducing the problem a bit by settling on one compiler takes away too much > > > freedom: > > > * The reference compiler is "dmd", which is also the fastest compiler, > > > but has a non-free and outdated backend and only supports x86/amd64. > > > * The two D compilers using GCC and LLVM as backends are of equal quality, > > > but both sometimes have quirks where it helps using the other temporarily. > > > * GCC is still considering the inclusion of D, but at the moment this > > > requires > > > patching the sources. > > > > Hello, > > > > I read your email about the Github repo. > > There are two options: > > 1) Move repo from Github to git.overlays.gentoo.org. > > 2) Move repo to Gentoo organization at Github. > > > > Which option would you like ? (option 1 is preferred since overlay runs > > under Gentoo infrastructure) > > > > Thanks, > > Pavlos > > Thanks for your reply. Since most D development happens on GitHub these days > option 2 means virtually all potential collaborators already have an account > and can easily make pull requests. So we'll chose that option. > What would happen with the existing 3 owners of gentoo-dlang under the > gentoo organization on GitHub? And can we still add people with push access > to the repository or would we have to ask an owner of the gentoo > organization to do that? I am in the owners team, can you please give me their names so i could add them to the team ?
Yes, but they don't know about their luck yet. I want to inform the other two first (and give them a chance to veto). Shouldn't take long.
(In reply to Marco Leise from comment #4) > Yes, but they don't know about their luck yet. I want to inform the other > two first (and give them a chance to veto). Shouldn't take long. OK, however i set up a repo[1] and gave you push access. Whenever you are ready change the remotes and push repo there or use the transfer option[2] that Github provides. [1] https://github.com/gentoo/dlang [2] https://help.github.com/articles/how-to-transfer-a-repository
Overlay moved and added to repositories.xml
