digitalmars.D.announce - Arch Linux D news digest
- Dicebot (65/65) Aug 25 2013 Greetings to fellow Arch Linux users - quite a lot of stuff has
- Johannes Pfau (5/11) Aug 25 2013 Awesome!
- Dicebot (3/15) Aug 25 2013 Nice, which is the current FE version supported then? (Will do an
- Iain Buclaw (5/24) Aug 25 2013 If it's sync'd with master, then it's 2.063.2. :)
- Jordi Sayol (13/98) Aug 25 2013 Is it not better:
- Dicebot (7/19) Aug 25 2013 Same here (blush)
- John Colvin (6/77) Aug 25 2013 OT:
- Tobias Pankrath (13/18) Aug 26 2013 I'm using Arch for quite a while now. It does take considerably
- Jonathan M Davis (10/34) Aug 26 2013 Arch is fantastic if you're willing to get your hands dirty a bit. It's
- Atila Neves (13/18) Aug 26 2013 I switched to Arch from Kubuntu a few months ago and I'm never
- Dicebot (15/20) Aug 26 2013 I liked it more in pre-systemd epoch, miss that `rc.conf`
- Andrei Alexandrescu (3/8) Aug 25 2013 Awesome! Please let me know when this is ready to go on reddit etc.
- Dicebot (3/13) Aug 26 2013 Now ;)
- Andrei Alexandrescu (5/18) Aug 26 2013 Ask, and ye shall receive :o).
- Jacob Carlborg (10/14) Aug 25 2013 I was about to tag dstep for a new release but I wanted to make a proper...
- Dicebot (8/15) Aug 26 2013 Can you please send me an e-mail with more details about it?
- Dicebot (6/6) Aug 26 2013 P.S.
- Atila Neves (6/6) Aug 26 2013 I should've read this more carefully. Updated my system tonight
- Dicebot (6/12) Aug 26 2013 That is a long-standing issue. Unfortunately, initial package had
- Atila Neves (5/20) Aug 26 2013 I get why the changes were made, I just hadn't noticed when I
- Dicebot (4/4) Oct 02 2013 Small Archy update:
- Kozzi (2/6) Oct 02 2013
- Kozzi (13/17) Oct 04 2013 I just found one problem with yours packages. The structure of
- Dicebot (5/24) Oct 05 2013 Thanks for report, this is mistake in the install script (those
- hsul (4/8) Oct 10 2013 Good Job!
- Dicebot (4/7) Oct 10 2013 Arch Linux policies prohibit pure source packages (there are
- Jonathan M Davis (4/13) Oct 11 2013 Also, last I heard, qtd was effectively dead. But I agree that D librari...
- Atila Neves (8/12) Nov 16 2013 I think the gdc installation is missing files. I can compile
- Moritz Maxeiner (4/19) Nov 17 2013 If you installed "gdc", did you install "libgphobos-devel"?
- simendsjo (5/28) Nov 17 2013 It's a known bug. This file should have been generated by some
Greetings to fellow Arch Linux users - quite a lot of stuff has happened there recently in relation to D and this should sum it up. Some changes may have not been synchronised to all mirrors yet, so please wait a bit before reporting :) ------------------------------------------------------ Changes ------------------------------------------------------ 1) After long period of bothering him with package change proposals previous D maintainer, Sven-Hendrik Haase, decided to transfer responsibilities for their maintenance to me. After formal voting I have been added to Trusted User list with intention to take care of anything D-related in Arch Linux. 2) `gdc` package has been added to the [community]. It uses 4.8.1 branch to match gcc version in Arch repositories. I know this one is relatively old and hope to fix this one day with Iain's help ;) 3) All D compilers now have common naming/path convention. Library: - libphobos.a - liblphobos.a - libgphobos.a Imports: - /usr/include/dlang/dmd - /usr/include/dlang/ldc - /usr/include/dlang/gdc/{gcc-version} 4) Four package groups has been defined: 'dlang', 'dlang-dmd', 'dlang-ldc', 'dlang-gdc'. Those can used as install/remove targets for pacman to get full development stack. 5) More preparations for shared library support. `libphobos` package currently contains only libphobos.so (with fixed SONAME) and is intended to be used as a dependency for user applications. Static library and import sources are available via `libphobos-devel`. GDC and LDC currently have only "-devel" versions of phobos as they don't seem to provide share one (I will be happy to add one if I am wrong). 6) `dtools` package now also provides DustMite! ------------------------------------------------------ Sources & bug reports ------------------------------------------------------ I am inevitably going to screw something at at some point and you will inevitably want to make a tweaked versions of official packages in AUR. Official Arch Linux stuff: [community] bug tracker: https://bugs.archlinux.org/index.php?project=5&do=index&switch=1 packaging script sources: https://projects.archlinux.org/svntogit/community.git/tree/trunk?h=packages/{package-name} However, I do prefer git/Github for development and exact mirror can be found here (together with my AUR packages): https://github.com/Dicebot/Arch-PKGBUILDs Both accepting pull requests and checking for bug reports there. ------------------------------------------------------ Adding new D packages ------------------------------------------------------ https://wiki.archlinux.org/index.php/AUR_Trusted_User_Guidelines#The_TU_and_.5Bcommunity.5D.2C_Guidelines_for_Package_Maintenance : "Only "popular" packages may enter the repo, as defined by 1% usage from pkgstats or 10 votes on the AUR." Yes, that is correct. I have a legitimate reasons to move any D package from AUR to [community] once it reaches 10 votes. Please don't forget to vote! At least tools like `dub` and `dstep`, in my opinion, are prime candidates for inclusion ;) If there are any D packages that match that criteria and I have missed it - please, ping me via public dicebot.lv or on IRC (Dicebot irc.freenode.net)
Aug 25 2013
Am Sun, 25 Aug 2013 21:11:51 +0200 schrieb "Dicebot" <public dicebot.lv>:Greetings to fellow Arch Linux users - quite a lot of stuff has happened there recently in relation to D and this should sum it up. Some changes may have not been synchronised to all mirrors yet, so please wait a bit before reporting :)Awesome! I updated the gdc-4.8 branch. (Well I actually just synced it with master which is still compatible with gcc-4.8)
Aug 25 2013
On Sunday, 25 August 2013 at 19:45:38 UTC, Johannes Pfau wrote:Am Sun, 25 Aug 2013 21:11:51 +0200 schrieb "Dicebot" <public dicebot.lv>:Nice, which is the current FE version supported then? (Will do an update pretty soon)Greetings to fellow Arch Linux users - quite a lot of stuff has happened there recently in relation to D and this should sum it up. Some changes may have not been synchronised to all mirrors yet, so please wait a bit before reporting :)Awesome! I updated the gdc-4.8 branch. (Well I actually just synced it with master which is still compatible with gcc-4.8)
Aug 25 2013
On 25 August 2013 21:51, Dicebot <public dicebot.lv> wrote:On Sunday, 25 August 2013 at 19:45:38 UTC, Johannes Pfau wrote:If it's sync'd with master, then it's 2.063.2. :) -- Iain Buclaw *(p < e ? p++ : p) = (c & 0x0f) + '0';Am Sun, 25 Aug 2013 21:11:51 +0200 schrieb "Dicebot" <public dicebot.lv>:Nice, which is the current FE version supported then? (Will do an update pretty soon)Greetings to fellow Arch Linux users - quite a lot of stuff has happened there recently in relation to D and this should sum it up. Some changes may have not been synchronised to all mirrors yet, so please wait a bit before reporting :)Awesome! I updated the gdc-4.8 branch. (Well I actually just synced it with master which is still compatible with gcc-4.8)
Aug 25 2013
On 25/08/13 21:11, Dicebot wrote:Greetings to fellow Arch Linux users - quite a lot of stuff has happened there recently in relation to D and this should sum it up. Some changes may have not been synchronised to all mirrors yet, so please wait a bit before reporting :) ------------------------------------------------------ Changes ------------------------------------------------------ 1) After long period of bothering him with package change proposals previous D maintainer, Sven-Hendrik Haase, decided to transfer responsibilities for their maintenance to me. After formal voting I have been added to Trusted User list with intention to take care of anything D-related in Arch Linux.Congratulations! :-)2) `gdc` package has been added to the [community]. It uses 4.8.1 branch to match gcc version in Arch repositories. I know this one is relatively old and hope to fix this one day with Iain's help ;) 3) All D compilers now have common naming/path convention. Library: - libphobos.a - liblphobos.a - libgphobos.aIs it not better: - libphobos2.a - liblphobos2.a - libgphobos2.aImports: - /usr/include/dlang/dmd - /usr/include/dlang/ldc - /usr/include/dlang/gdc/{gcc-version}Current debian path is without "dlang" directory, but I think that this is not a problem.4) Four package groups has been defined: 'dlang', 'dlang-dmd', 'dlang-ldc', 'dlang-gdc'. Those can used as install/remove targets for pacman to get full development stack. 5) More preparations for shared library support. `libphobos` package currently contains only libphobos.so (with fixed SONAME) and is intended to be used as a dependency for user applications.Is it not better: - libphobos2.so What's the Arch Linux way to name shared libraries? On debian, "libphobos2.so" (libphobos2-dev) is a symlink to real "libphobos2.so.0.63.0" (libphobos2-63) shared library. "libphobos2.so.0.63" (libphobos2-63) SONAME symlink is created with the "ldconfig" command during the deb package (un)installation.Static library and import sources are available via `libphobos-devel`. GDC and LDC currently have only "-devel" versions of phobos as they don't seem to provide share one (I will be happy to add one if I am wrong). 6) `dtools` package now also provides DustMite! ------------------------------------------------------ Sources & bug reports ------------------------------------------------------ I am inevitably going to screw something at at some point and you will inevitably want to make a tweaked versions of official packages in AUR. Official Arch Linux stuff: [community] bug tracker: https://bugs.archlinux.org/index.php?project=5&do=index&switch=1 packaging script sources: https://projects.archlinux.org/svntogit/community.git/tree/trunk?h=packages/{package-name} However, I do prefer git/Github for development and exact mirror can be found here (together with my AUR packages): https://github.com/Dicebot/Arch-PKGBUILDs Both accepting pull requests and checking for bug reports there. ------------------------------------------------------ Adding new D packages ------------------------------------------------------ https://wiki.archlinux.org/index.php/AUR_Trusted_User_Guidelines#The_TU_and_.5Bcommunity.5D.2C_Guidelines_for_Package_Maintenance : "Only "popular" packages may enter the repo, as defined by 1% usage from pkgstats or 10 votes on the AUR." Yes, that is correct. I have a legitimate reasons to move any D package from AUR to [community] once it reaches 10 votes. Please don't forget to vote! At least tools like `dub` and `dstep`, in my opinion, are prime candidates for inclusion ;) If there are any D packages that match that criteria and I have missed it - please, ping me via public dicebot.lv or on IRC (Dicebot irc.freenode.net)Great work! awesome! -- Jordi Sayol
Aug 25 2013
On Sunday, 25 August 2013 at 20:33:49 UTC, Jordi Sayol wrote:Is it not better: - libphobos2.a - liblphobos2.a - libgphobos2.aIt is libphobos2.a, of course, typo-paste :)Is it not better: - libphobos2.soSame here (blush)What's the Arch Linux way to name shared libraries? On debian, "libphobos2.so" (libphobos2-dev) is a symlink to real "libphobos2.so.0.63.0" (libphobos2-63) shared library. "libphobos2.so.0.63" (libphobos2-63) SONAME symlink is created with the "ldconfig" command during the deb package (un)installation.On Arch currently there are only libphobos2.so (actualy binary) and libphobos2.so.0.63 (automatically created during installation). I am going to ask on IRC if any other symlinks are expected.
Aug 25 2013
On 08/25/2013 10:48 PM, Dicebot wrote:> On Sunday, 25 August 2013 at 20:33:49 UTC, Jordi Sayol wrote:Usually the actual binary has the fully qualified version number, and libphobos2.so would be included/created by the devel package. This would allow someone to install multiple versions of the same lib side by side if needed. Also Archlinux usually doesn't have devel packages, the headers, libraries and documentation are included in the regular package. -- Mike WeyWhat's the Arch Linux way to name shared libraries? On debian, "libphobos2.so" (libphobos2-dev) is a symlink to real "libphobos2.so.0.63.0" (libphobos2-63) shared library. "libphobos2.so.0.63" (libphobos2-63) SONAME symlink is created with the "ldconfig" command during the deb package (un)installation.On Arch currently there are only libphobos2.so (actualy binary) and libphobos2.so.0.63 (automatically created during installation). I am going to ask on IRC if any other symlinks are expected.
Aug 26 2013
On Monday, 26 August 2013 at 10:52:23 UTC, Mike Wey wrote:Usually the actual binary has the fully qualified version number, and libphobos2.so would be included/created by the devel package.Yes, that does seem to be the case with other packages, I am simply reluctant to make any steps further from upstream until I have carefully studied that domain - and shared library deployment is not something I am very familiar with. It is number one topic on my TODO list.Also Archlinux usually doesn't have devel packages, the headers, libraries and documentation are included in the regular package.It was a subject to hot 30min long debate on clode #archlinux-tu channel, not only my personal decision :) For normal packages difference between dependency environment and development environment is not that important - but for compiled languages it does matter. Pulling in all D development stack for a single application written in D is quite inconvenient for an end user. Done similarly in gcc - stdlib headers are part of gcc package, but libstdc++ has its own. `-devel` packages are rare on Arch, but they do exist.
Aug 26 2013
On Sunday, 25 August 2013 at 19:11:52 UTC, Dicebot wrote:Greetings to fellow Arch Linux users - quite a lot of stuff has happened there recently in relation to D and this should sum it up. Some changes may have not been synchronised to all mirrors yet, so please wait a bit before reporting :) ------------------------------------------------------ Changes ------------------------------------------------------ 1) After long period of bothering him with package change proposals previous D maintainer, Sven-Hendrik Haase, decided to transfer responsibilities for their maintenance to me. After formal voting I have been added to Trusted User list with intention to take care of anything D-related in Arch Linux. 2) `gdc` package has been added to the [community]. It uses 4.8.1 branch to match gcc version in Arch repositories. I know this one is relatively old and hope to fix this one day with Iain's help ;) 3) All D compilers now have common naming/path convention. Library: - libphobos.a - liblphobos.a - libgphobos.a Imports: - /usr/include/dlang/dmd - /usr/include/dlang/ldc - /usr/include/dlang/gdc/{gcc-version} 4) Four package groups has been defined: 'dlang', 'dlang-dmd', 'dlang-ldc', 'dlang-gdc'. Those can used as install/remove targets for pacman to get full development stack. 5) More preparations for shared library support. `libphobos` package currently contains only libphobos.so (with fixed SONAME) and is intended to be used as a dependency for user applications. Static library and import sources are available via `libphobos-devel`. GDC and LDC currently have only "-devel" versions of phobos as they don't seem to provide share one (I will be happy to add one if I am wrong). 6) `dtools` package now also provides DustMite! ------------------------------------------------------ Sources & bug reports ------------------------------------------------------ I am inevitably going to screw something at at some point and you will inevitably want to make a tweaked versions of official packages in AUR. Official Arch Linux stuff: [community] bug tracker: https://bugs.archlinux.org/index.php?project=5&do=index&switch=1 packaging script sources: https://projects.archlinux.org/svntogit/community.git/tree/trunk?h=packages/{package-name} However, I do prefer git/Github for development and exact mirror can be found here (together with my AUR packages): https://github.com/Dicebot/Arch-PKGBUILDs Both accepting pull requests and checking for bug reports there. ------------------------------------------------------ Adding new D packages ------------------------------------------------------ https://wiki.archlinux.org/index.php/AUR_Trusted_User_Guidelines#The_TU_and_.5Bcommunity.5D.2C_Guidelines_for_Package_Maintenance : "Only "popular" packages may enter the repo, as defined by 1% usage from pkgstats or 10 votes on the AUR." Yes, that is correct. I have a legitimate reasons to move any D package from AUR to [community] once it reaches 10 votes. Please don't forget to vote! At least tools like `dub` and `dstep`, in my opinion, are prime candidates for inclusion ;) If there are any D packages that match that criteria and I have missed it - please, ping me via public dicebot.lv or on IRC (Dicebot irc.freenode.net)OT: This might be the final straw that takes me over to Arch. How are things over on that side of linux? I've been using ubuntu/lubuntu/fedora/mint on various machines for years but never really tried out the more DIY distros.
Aug 25 2013
On Sunday, 25 August 2013 at 22:35:50 UTC, John Colvin wrote:OT: This might be the final straw that takes me over to Arch. How are things over on that side of linux? I've been using ubuntu/lubuntu/fedora/mint on various machines for years but never really tried out the more DIY distros.I'm using Arch for quite a while now. It does take considerably longer to setup, especially the first time. I'd say, you should only do it, if you like to tinker with your system. There are some configuration 'errors' from time to time. So I needed to manually add some udev rules and change file permissions to make my printer fly recently. Also you'll encounter problems during updates that need manual intervention. Reading the news at archlinux.org before updating is a must. That said, you don't have more issues with Arch than with any other distro. Maybe other issues. And you get the newest software and an easy way to rebuild packages or make your own.
Aug 26 2013
On Monday, August 26, 2013 09:09:02 Tobias Pankrath wrote:On Sunday, 25 August 2013 at 22:35:50 UTC, John Colvin wrote:Arch is fantastic if you're willing to get your hands dirty a bit. It's nowhere near as hard to use as Gentoo is, but it does take a fair but of manual setup and management. I definitely wouldn't call it newbie-friendly. But it's by the easiest distro that I've ever used for having bleeding edge software, and everything is vanilla instead of being screwed with to make distro-specific. So, if you're willing to tinker a bit, it's well worth it IMHO, and for the most part, once it's going, it's not that hard to keep it going, but don't use it if you want something that "just works." - Jonathan M DavisOT: This might be the final straw that takes me over to Arch. How are things over on that side of linux? I've been using ubuntu/lubuntu/fedora/mint on various machines for years but never really tried out the more DIY distros.I'm using Arch for quite a while now. It does take considerably longer to setup, especially the first time. I'd say, you should only do it, if you like to tinker with your system. There are some configuration 'errors' from time to time. So I needed to manually add some udev rules and change file permissions to make my printer fly recently. Also you'll encounter problems during updates that need manual intervention. Reading the news at archlinux.org before updating is a must. That said, you don't have more issues with Arch than with any other distro. Maybe other issues. And you get the newest software and an easy way to rebuild packages or make your own.
Aug 26 2013
I switched to Arch from Kubuntu a few months ago and I'm never looking back. It's definitely not for everyone since setting up is a pain and some favour stability over having the newest, shiny toys. For me, I wanted a distro that has the latest and greatest that I can make as minimal as possible, with a great package management system. And that's Arch. Give it a whirl in a VM and judge for yourself. I was worried for a while about leaving the Ubuntu-derived distros and missing out on packages but Arch seems to have everything I want in the official repositories. In the rare case it doesn't, it's in the AUR and easily installed anyway. To the original poster: thanks and good work! AtilaOT: This might be the final straw that takes me over to Arch. How are things over on that side of linux? I've been using ubuntu/lubuntu/fedora/mint on various machines for years but never really tried out the more DIY distros.
Aug 26 2013
On Sunday, 25 August 2013 at 22:35:50 UTC, John Colvin wrote:OT: This might be the final straw that takes me over to Arch. How are things over on that side of linux? I've been using ubuntu/lubuntu/fedora/mint on various machines for years but never really tried out the more DIY distros.I liked it more in pre-systemd epoch, miss that `rc.conf` elegance. It even had ncurses-based installer then! :) Right now the crucial point for me is AUR / PKGBUILD system (and the reason why I wasn't satisfied with any other distro I have tried). Creating own packages is incredibly easy and simple, as well as sharing them with people. It helps to keep system clean if you build own stuff from sources and allows Arch to be the true bleeding edge distro - even if main repository maintainer are slow or reluctant to include some new shiny program, community will do it in AUR anyway. That was the case initially with D2, btw - it has started in AUR. Reading manuals / wiki is pretty much mandatory but I don't think it is a major blocker for a programmer, unless he is completely new to Linux :)
Aug 26 2013
On 8/25/13 12:11 PM, Dicebot wrote:Greetings to fellow Arch Linux users - quite a lot of stuff has happened there recently in relation to D and this should sum it up. Some changes may have not been synchronised to all mirrors yet, so please wait a bit before reporting :)Awesome! Please let me know when this is ready to go on reddit etc. Andrei
Aug 25 2013
On Sunday, 25 August 2013 at 23:17:22 UTC, Andrei Alexandrescu wrote:On 8/25/13 12:11 PM, Dicebot wrote:Now ;)Greetings to fellow Arch Linux users - quite a lot of stuff has happened there recently in relation to D and this should sum it up. Some changes may have not been synchronised to all mirrors yet, so please wait a bit before reporting :)Awesome! Please let me know when this is ready to go on reddit etc. Andrei
Aug 26 2013
On 8/26/13 5:28 AM, Dicebot wrote:On Sunday, 25 August 2013 at 23:17:22 UTC, Andrei Alexandrescu wrote:Ask, and ye shall receive :o). http://www.reddit.com/r/programming/comments/1l4r01/improved_d_presence_on_arch_linux_latest_releases/ Upvote!!! AndreiOn 8/25/13 12:11 PM, Dicebot wrote:Now ;)Greetings to fellow Arch Linux users - quite a lot of stuff has happened there recently in relation to D and this should sum it up. Some changes may have not been synchronised to all mirrors yet, so please wait a bit before reporting :)Awesome! Please let me know when this is ready to go on reddit etc. Andrei
Aug 26 2013
On 2013-08-25 21:11, Dicebot wrote:Yes, that is correct. I have a legitimate reasons to move any D package from AUR to [community] once it reaches 10 votes. Please don't forget to vote! At least tools like `dub` and `dstep`, in my opinion, are prime candidates for inclusion ;)I was about to tag dstep for a new release but I wanted to make a proper release as well, providing pre-compiled binaries and so on. Unfortunately I haven't been able to produce a working binary on Linux 32bit, which is weird since it only worked on 32bit before. It segfaults some where inside libclang. I've moved from Ubuntu to Debian in the hope of better binary compatibility, I'm wondering if that's the reason. -- /Jacob Carlborg
Aug 25 2013
On Monday, 26 August 2013 at 06:55:50 UTC, Jacob Carlborg wrote:I was about to tag dstep for a new release but I wanted to make a proper release as well, providing pre-compiled binaries and so on. Unfortunately I haven't been able to produce a working binary on Linux 32bit, which is weird since it only worked on 32bit before. It segfaults some where inside libclang. I've moved from Ubuntu to Debian in the hope of better binary compatibility, I'm wondering if that's the reason.Can you please send me an e-mail with more details about it? Current master works for me on both 32-bit and 64-bit Arch Linux test virtual machines. You may have an issue with libclang - Debian does to really provide better binary compatibility, it provides stability. And that may go bad when you require relatively versions of binaries (3.2+ afair for libclang). One more reason why I prefer bleeding edge for development :)
Aug 26 2013
P.S. I have recently found that D has an entry on Arch Wiki: https://wiki.archlinux.org/index.php/D_%28programming_language%29 It is quite out of date now and I am quite busy :) But, hey, it is a wiki, any fellow Arch user can go there and edit it! Volunteers are appreciated ;)
Aug 26 2013
I should've read this more carefully. Updated my system tonight and was missing the phobos imports, took a while to figure out why. For anyone else out there, TL;DR Install the lib{,g,l}phobos-devel, or one of dlang-dmd, dlang-gdc, dlang-ldc. Or just dlang for the lot. Atila
Aug 26 2013
On Monday, 26 August 2013 at 19:45:45 UTC, Atila Neves wrote:I should've read this more carefully. Updated my system tonight and was missing the phobos imports, took a while to figure out why. For anyone else out there, TL;DR Install the lib{,g,l}phobos-devel, or one of dlang-dmd, dlang-gdc, dlang-ldc. Or just dlang for the lot. AtilaThat is a long-standing issue. Unfortunately, initial package had a harmful choice of `dmd` package having a hard dependency on `libphobos` and changing expectations in that direction hard. I was not able to think anything better as listing it in optdepends and providing `dlang-dmd` group. And suggestions are appreciated.
Aug 26 2013
I get why the changes were made, I just hadn't noticed when I read the original post that there was user intervention needed to keep the status quo. Atila On Monday, 26 August 2013 at 20:41:40 UTC, Dicebot wrote:On Monday, 26 August 2013 at 19:45:45 UTC, Atila Neves wrote:I should've read this more carefully. Updated my system tonight and was missing the phobos imports, took a while to figure out why. For anyone else out there, TL;DR Install the lib{,g,l}phobos-devel, or one of dlang-dmd, dlang-gdc, dlang-ldc. Or just dlang for the lot. AtilaThat is a long-standing issue. Unfortunately, initial package had a harmful choice of `dmd` package having a hard dependency on `libphobos` and changing expectations in that direction hard. I was not able to think anything better as listing it in optdepends and providing `dlang-dmd` group. And suggestions are appreciated.
Aug 26 2013
Small Archy update: 1) dub has been just adopted into [community] 2) all three compiler phobos versions now provide 'd-runtime` and `d-stdlib` meta-dependencies
Oct 02 2013
Good job :) On Wednesday, 2 October 2013 at 15:14:08 UTC, Dicebot wrote:Small Archy update: 1) dub has been just adopted into [community] 2) all three compiler phobos versions now provide 'd-runtime` and `d-stdlib` meta-dependencies
Oct 02 2013
On Wednesday, 2 October 2013 at 15:14:08 UTC, Dicebot wrote:Small Archy update: 1) dub has been just adopted into [community] 2) all three compiler phobos versions now provide 'd-runtime` and `d-stdlib` meta-dependenciesI just found one problem with yours packages. The structure of druntime and phobos imports is not perfect. Now we have druntime/import in same directory as phobos import. This cause problems with ddt for eg. Because in ddt it is not allowed to add imports, which are place in directory which is already used as a import directory. So in DDT only phobos imports works as expected, but not the druntime (core...). It would be better if druntime and phobos has been moved to separate directory. Something like: phobos in /usr/include/dlang/dmd/phobos druntime in /usr/include/dlang/dmd/druntime (same as is now)
Oct 04 2013
On Friday, 4 October 2013 at 20:21:07 UTC, Kozzi wrote:On Wednesday, 2 October 2013 at 15:14:08 UTC, Dicebot wrote:Thanks for report, this is mistake in the install script (those two folders should be merged into one based on reference archive). Can you please create an issue on topic here : https://github.com/Dicebot/Arch-PKGBUILDs ?Small Archy update: 1) dub has been just adopted into [community] 2) all three compiler phobos versions now provide 'd-runtime` and `d-stdlib` meta-dependenciesI just found one problem with yours packages. The structure of druntime and phobos imports is not perfect. Now we have druntime/import in same directory as phobos import. This cause problems with ddt for eg. Because in ddt it is not allowed to add imports, which are place in directory which is already used as a import directory. So in DDT only phobos imports works as expected, but not the druntime (core...). It would be better if druntime and phobos has been moved to separate directory. Something like: phobos in /usr/include/dlang/dmd/phobos druntime in /usr/include/dlang/dmd/druntime (same as is now)
Oct 05 2013
Good Job! What's about gtkd, qtd? I'd love to see them in the official repositories :-) On Wednesday, 2 October 2013 at 15:14:08 UTC, Dicebot wrote:Small Archy update: 1) dub has been just adopted into [community] 2) all three compiler phobos versions now provide 'd-runtime` and `d-stdlib` meta-dependencies
Oct 10 2013
On Thursday, 10 October 2013 at 18:43:32 UTC, hsul wrote:Good Job! What's about gtkd, qtd? I'd love to see them in the official repositories :-)Arch Linux policies prohibit pure source packages (there are always exception but it is not the case). I tend to agree, such stuff makes much more sense in dub registry.
Oct 10 2013
On Thursday, October 10, 2013 20:49:01 Dicebot wrote:On Thursday, 10 October 2013 at 18:43:32 UTC, hsul wrote:Also, last I heard, qtd was effectively dead. But I agree that D libraries belong in dub, not in packages for OS package managers. - Jonathan M DavisGood Job! What's about gtkd, qtd? I'd love to see them in the official repositories :-)Arch Linux policies prohibit pure source packages (there are always exception but it is not the case). I tend to agree, such stuff makes much more sense in dub registry.
Oct 11 2013
On Wednesday, 2 October 2013 at 15:14:08 UTC, Dicebot wrote:Small Archy update: 1) dub has been just adopted into [community] 2) all three compiler phobos versions now provide 'd-runtime` and `d-stdlib` meta-dependenciesI think the gdc installation is missing files. I can compile simple programs easily enough, but importing core.runtime causes this: /usr/include/dlang/gdc/4.8.2/gcc/backtrace.d:22: Error: module libbacktrace is in file 'gcc/libbacktrace.d' which cannot be read And, sure enough, there is no such libbacktrace.d to be found. This is problematic since I can't compile anything with dub.
Nov 16 2013
On Saturday, 16 November 2013 at 12:49:05 UTC, Atila Neves wrote:On Wednesday, 2 October 2013 at 15:14:08 UTC, Dicebot wrote:If you installed "gdc", did you install "libgphobos-devel"? Without the latter you have neither druntime, nor phobos (and as such not libbacktrace.d).Small Archy update: 1) dub has been just adopted into [community] 2) all three compiler phobos versions now provide 'd-runtime` and `d-stdlib` meta-dependenciesI think the gdc installation is missing files. I can compile simple programs easily enough, but importing core.runtime causes this: /usr/include/dlang/gdc/4.8.2/gcc/backtrace.d:22: Error: module libbacktrace is in file 'gcc/libbacktrace.d' which cannot be read And, sure enough, there is no such libbacktrace.d to be found. This is problematic since I can't compile anything with dub.
Nov 17 2013
On Sunday, 17 November 2013 at 10:44:56 UTC, Moritz Maxeiner wrote:On Saturday, 16 November 2013 at 12:49:05 UTC, Atila Neves wrote:It's a known bug. This file should have been generated by some text templating engine. Dont remember where I posted the issue, but the maintainer is aware of the issue.On Wednesday, 2 October 2013 at 15:14:08 UTC, Dicebot wrote:If you installed "gdc", did you install "libgphobos-devel"? Without the latter you have neither druntime, nor phobos (and as such not libbacktrace.d).Small Archy update: 1) dub has been just adopted into [community] 2) all three compiler phobos versions now provide 'd-runtime` and `d-stdlib` meta-dependenciesI think the gdc installation is missing files. I can compile simple programs easily enough, but importing core.runtime causes this: /usr/include/dlang/gdc/4.8.2/gcc/backtrace.d:22: Error: module libbacktrace is in file 'gcc/libbacktrace.d' which cannot be read And, sure enough, there is no such libbacktrace.d to be found. This is problematic since I can't compile anything with dub.
Nov 17 2013