| 1 |
On Thu, Oct 30, 2008 at 2:34 PM, Volker Armin Hemmann |
| 2 |
<volker.armin.hemmann@××××××××××××.de> wrote: |
| 3 |
> On Donnerstag 30 Oktober 2008, Helmut Jarausch wrote: |
| 4 |
>> On 30 Oct, Volker Armin Hemmann wrote: |
| 5 |
>> > Hi, |
| 6 |
>> > |
| 7 |
>> > I have the same 'problem'. Which portage version are you using? |
| 8 |
>> |
| 9 |
>> I'm using portage-2.2_rc12 on amd64 hardware. |
| 10 |
> |
| 11 |
> same here. |
| 12 |
> |
| 13 |
> Would nice to know the version from peoples without the problem. |
| 14 |
|
| 15 |
In my case, I've never used buildpkg feature and my |
| 16 |
/usr/portage/packages is empty. After reading this thread, I decided |
| 17 |
to enable it and emerge something small to see what comes out. |
| 18 |
|
| 19 |
After emerging, I do not have an All directory, and there are no |
| 20 |
symlinks. It put the package file directly in |
| 21 |
/usr/portage/packages/app-arch/zip-3.0.tbz2 and generated a |
| 22 |
/usr/portage/packages/Packages file with some info in it. |
| 23 |
|
| 24 |
In make.conf my PKGDIR is not set, so I'm using default... |
| 25 |
|
| 26 |
My profile is default/linux/amd64/2008.0/desktop |
| 27 |
|
| 28 |
good luck :) |
| 29 |
|
| 30 |
paul |
Archives