| 1 |
Neil Bothwick wrote: |
| 2 |
> On Mon, 28 Sep 2009 13:23:24 +0100, Steve wrote: |
| 3 |
> |
| 4 |
>> I guess I need to do something special to get the 'gnustep overlay'... |
| 5 |
>> I've recently done my eix-sync, so that's not it. |
| 6 |
>> |
| 7 |
> emerge layman and run "eix-remote update" |
| 8 |
> |
| 9 |
Many thanks, I now get the same eix response as you posted... unfortunately: |
| 10 |
|
| 11 |
% emerge sogo |
| 12 |
Calculating dependencies... done! |
| 13 |
|
| 14 |
>>> Verifying ebuild manifests |
| 15 |
|
| 16 |
!!! A file listed in the Manifest could not be found: |
| 17 |
/usr/local/portage/layman/gnustep/gnustep-libs/sope/sope-4.7_pre20090616.ebuild |
| 18 |
% ls /usr/local/portage/layman/gnustep/gnustep-libs/sope |
| 19 |
Manifest files sope-4.7_pre20080521.ebuild |
| 20 |
% |
| 21 |
|
| 22 |
It looks, at first glance, as if there's a good reason for the packages |
| 23 |
to be masked... I added gnustep-apps/sogo and gnustep-libs/sope with a |
| 24 |
~x86 keyword, and added objc to my package.use... but had hoped to be |
| 25 |
able to try sogo without having to do too much grunging about with |
| 26 |
installation details... At the moment, I don't even know if it is |
| 27 |
suitable for my project... :) |
Archives