Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 263644 - DBD-Pg-2.11.8.ebuild -> No $EROOT -> install failed (but without error)
Summary: DBD-Pg-2.11.8.ebuild -> No $EROOT -> install failed (but without error)
Status: RESOLVED FIXED
Alias: None
Product: Gentoo/Alt
Classification: Unclassified
Component: Prefix Support (show other bugs)
Hardware: All All
: High normal (vote)
Assignee: Gentoo Prefix
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-24 18:28 UTC by Denis Knauf
Modified: 2009-03-24 18:40 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
DBD-Pg-2.11.8.ebuild.patch (patch,837 bytes, patch)
2009-03-24 18:29 UTC, Denis Knauf
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Denis Knauf 2009-03-24 18:28:07 UTC
This ebuild has some paths without $EROOT, so it will fail. But if you install it, you don't get any error.
Comment 1 Denis Knauf 2009-03-24 18:29:04 UTC
Created attachment 186136 [details, diff]
DBD-Pg-2.11.8.ebuild.patch
Comment 2 Denis Knauf 2009-03-24 18:33:11 UTC
Excuse me, this patch was the wrong. virtual/perl-version is needed of course!
Comment 3 Jeremy Olexa (darkside) (RETIRED) archtester gentoo-dev Security 2009-03-24 18:40:53 UTC
(In reply to comment #1)
> Created an attachment (id=186136) [edit]
> DBD-Pg-2.11.8.ebuild.patch
> 

Actually, they should be EPREFIX there. And I didn't add the second one becuase
it would result in a double path.

%% postgres_include="$(readlink -f ${EPREFIX}/usr/include/postgresql)"
%% postgres_lib="${postgres_include//include/lib}"
%% echo $postgres_lib 
/home/jolexa/portage/linux-64/usr/lib/postgresql

I'm still not convinced the ebuild is correct though.

%% ls /home/jolexa/portage/linux-64/usr/lib/postgresql
ls: cannot access /home/jolexa/portage/linux-64/usr/lib/postgresql: No such
file or directory
%% ls /home/jolexa/portage/linux-64/usr/lib/postgresql-8.3/
bin/  lib/

Resolving as fixed because the issue reported is indeed fixed, there may be
other issues though.