On Wednesday, 9 October 2013 at 12:23:40 UTC, safety0ff wrote:
> On Wednesday, 9 October 2013 at 07:03:48 UTC, Kai Nacke wrote:
>> Why not use the gentoo-overlay (see http://wiki.dlang.org/Installing_LDC_on_Gentoo)?
>>
>> Kai
>
> 1. Gentoo overlay doesn't have an alpha ebuild.

Yes, that is right. But it has the 9999-ebuild which is currently the same as the 0.12 release.
Nevertheless if you create an ebuild be sure to provide a pull request for it.

> 2. Gentoo overlay ebuild looks like it installs some files directly instead of to the temporary image directory first and letting portage do the rest.

This should not be. If you can specify the file(s) then please file an issue.

Kai

On Wednesday, 9 October 2013 at 12:30:55 UTC, Kai Nacke wrote:
> Nevertheless if you create an ebuild be sure to provide a pull request for it.
Will do, but ATM I'm blocked on getting the source.
I could look up the git sha1's manually, but that becomes a maintenance burden, I'd rather deal with tags instead.

On Wednesday, 9 October 2013 at 13:11:34 UTC, safety0ff wrote:
> On Wednesday, 9 October 2013 at 12:30:55 UTC, Kai Nacke wrote:
>> Nevertheless if you create an ebuild be sure to provide a pull request for it.
> Will do, but ATM I'm blocked on getting the source.
> I could look up the git sha1's manually, but that becomes a maintenance burden, I'd rather deal with tags instead.

What about using branch origin/release-0.12.0 as starting point?

Kai

On Wed, Oct 9, 2013 at 3:11 PM, safety0ff <safety0ff.dev@gmail.com> wrote:
> Will do, but ATM I'm blocked on getting the source.
> I could look up the git sha1's manually, but that becomes a maintenance
> burden, I'd rather deal with tags instead.

We use Git submodules for druntime, Phobos and dmd-testsuite. This means that they are tied into the main repository via a specific commit ID, so the v0.12.0-alpha1 tag in the LDC repository unambiguously identifies the druntime/Phobos versions to use.

Not having to manually maintain the cross-dependencies between repositories, which is rather error-prone, is actually one of the few advantages of submodules.

David

On Wed, Oct 9, 2013 at 1:03 PM, Kai Nacke <kai@redstar.de> wrote:
> Oh, I missed the edit button. Done.

Okay, great. Could you maybe make a pass over the release notes at some point too, particularly regarding your platform support work? I typed these up in a hurry while waiting for the builds to complete, so there might still be silly mistakes and major omissions.

Thanks!
David

On Wednesday, 9 October 2013 at 13:54:29 UTC, David Nadlinger wrote:
> We use Git submodules for druntime, Phobos and dmd-testsuite. This means that they are tied into the main repository via a specific
> commit ID, so the v0.12.0-alpha1 tag in the LDC repository
> unambiguously identifies the druntime/Phobos versions to use.
>
> Not having to manually maintain the cross-dependencies between
> repositories, which is rather error-prone, is actually one of the few advantages of submodules.
>
> David

Ok, I've looked over some options an putting the SHA1's into the ebuild seems to be the best overall approach for testing builds.

I looked into scripting fetching SHA1's and it's possible but it's not as tidy.

Stable builds should have full source uploaded as is currently done.

As for the issues I mentioned, it seems I was fooled by paths that are input as absolute paths but used as relative paths when it comes to installation.

Nevertheless, I did "fix" the way bash-completion installation is handled.

I'll send a pull request soon.

On Wed, Oct 9, 2013 at 9:14 PM, safety0ff <safety0ff.dev@gmail.com> wrote:
> I looked into scripting fetching SHA1's and it's possible but it's not as tidy.

Why don't just use Git submodules as intended?

> Stable builds should have full source uploaded as is currently done.

Full source releases will be provided for the actual release, I just missed that the new GitHub release feature with its shiny source download buttons again doesn't include submodules in the packages.

David

Am 08.10.2013 23:00, schrieb David Nadlinger:
> Hi all,
>
> As discussed, here are the first alpha packages for the 0.12.0 release.
>
> See the GitHub release page for the download links and the preliminary
> change log:
> https://github.com/ldc-developers/ldc/releases/tag/v0.12.0-alpha1
>
> 353c4a8cfcf457575dfb8a27dfa6f61c ldc2-0.12.0-alpha1-linux-x86.tar.gz
> 0a56e5629f0e9d4c7860df0cf15961c1 ldc2-0.12.0-alpha1-linux-x86.tar.xz
> 81da36e25fe221a9e8ae24140dae0c7f ldc2-0.12.0-alpha1-linux-x86_64.tar.gz
> 790dcffc430018a36b9dbc65a545f802 ldc2-0.12.0-alpha1-linux-x86_64.tar.xz
> 02159c0d60399e74c1f9c4dd47073341 ldc2-0.12.0-alpha1-osx-x86_64.tar.gz
> 5a3fb0fef3544b0f4441a9aefb07d70f ldc2-0.12.0-alpha1-osx-x86_64.tar.xz
> 119b9419199afc85419fb09760eadf26  ldc2-0.12.0-alpha1-mingw-x86.7z
>
> Please be sure to report any regression at
> https://github.com/ldc-developers/ldc/issues.
>
> Thanks to everybody involved!
> David

I ran the windows version through a couple of small programms I have lying around and everything works fine so far.

The only issue I've found is, that when using curl it will lead to a linker error because ldmd2 will not automatically link against libcurl.

Also when passing -gs to ldmd2 it will cause the following error:
ldc2.exe: Unknown command line argument '-disable-fp-elim'.  Try: 'F:/ldc/bin/ldc2.exe -help'
ldc2.exe: Did you mean '-disable-asserts'?

Kind Regards
Benjamin Thaut

On Wed, Oct 9, 2013 at 9:40 PM, Benjamin Thaut <code@benjamin-thaut.de> wrote:
> I ran the windows version through a couple of small programms I have lying around and everything works fine so far.

Good to hear, thanks for testing.

> The only issue I've found is, that when using curl it will lead to a linker error because ldmd2 will not automatically link against libcurl.
>
> Also when passing -gs to ldmd2 it will cause the following error:
> ldc2.exe: Unknown command line argument '-disable-fp-elim'.  Try:
> 'F:/ldc/bin/ldc2.exe -help'
> ldc2.exe: Did you mean '-disable-asserts'?

Could you please post those two to the GitHub tracker? Thanks!

David

Am 09.10.2013 21:50, schrieb David Nadlinger:
> On Wed, Oct 9, 2013 at 9:40 PM, Benjamin Thaut <code@benjamin-thaut.de> wrote:
>> I ran the windows version through a couple of small programms I have lying
>> around and everything works fine so far.
>
> Good to hear, thanks for testing.
>
>> The only issue I've found is, that when using curl it will lead to a linker
>> error because ldmd2 will not automatically link against libcurl.
>>
>> Also when passing -gs to ldmd2 it will cause the following error:
>> ldc2.exe: Unknown command line argument '-disable-fp-elim'.  Try:
>> 'F:/ldc/bin/ldc2.exe -help'
>> ldc2.exe: Did you mean '-disable-asserts'?
>
> Could you please post those two to the GitHub tracker? Thanks!
>
> David
>

Done