As gentoo is too busy to insert my ebuilds I'll post them here...

Stephan Wienczny wrote:
> As gentoo is too busy to insert my ebuilds I'll post them here...
>
Thanks Stephan,

So do we just stick these in a directory in the portage tree and ebuild them?

I haven't done much with separate ebuilds apart from what appears in the portage tree.  Is handling these ebuilds any different?

Thanks,

John

John Reimer wrote:
> Stephan Wienczny wrote:
> 
>> As gentoo is too busy to insert my ebuilds I'll post them here...
>>
> Thanks Stephan,
> 
> So do we just stick these in a directory in the portage tree and ebuild them?
> 
> I haven't done much with separate ebuilds apart from what appears in the portage tree.  Is handling these ebuilds any different?
> 
> Thanks,
> 
> John

It's not that easy.
You should use portage overlay because the ebuilds are not deleted on your next emerge sync.
The directorys should be dev-lang/gdc and dev-lang/phobos.
Before you can emerge an package you have to run digest on it:
ebuild gdc-1.0.0_rc5.ebuild digest
ebuild phobos-1.0.0_rc5.ebuild digest
Then you can do emerge phobos and both should be installed

Stephan

Stephan Wienczny wrote:
[snip]
> You should use portage overlay because the ebuilds are not deleted on your next emerge sync.
> The directorys should be dev-lang/gdc and dev-lang/phobos.
> Before you can emerge an package you have to run digest on it:
> ebuild gdc-1.0.0_rc5.ebuild digest
> ebuild phobos-1.0.0_rc5.ebuild digest
> Then you can do emerge phobos and both should be installed

Sweet. Thanks for these Stephen, it really makes it easy. I hope Gentoo includes these soon. Worked like a charm for me.

Cheers,
  Craig

Cool, this should make trying out D much easier for me!

One thing though, shouldn't Phobos be in dev-libs instead of dev-lang?

Ian.

-- 
#ifndef  __COMMON_SENSE__ | Ian Phillips
#include <std_disclaimer> | TIBCO Software Inc.
#endif                    | www.tibco.com