3rd party ebuilds in local overlay not installing

Anything that pertains to Portage

Moderator: Moderators

3rd party ebuilds in local overlay not installing

Postby ddfusion » Mon Mar 30, 2009 3:31

every ebuild i have tried to install fails.
I have followed these instructions http://wiki.sabayonlinux.org/index.php? ... ty_Ebuilds

could it be the ebuilds are no good or am i missing something?
could anyone please help me thro this?

thanks
ddfusion
Baby Hen
 
Posts: 3
Joined: Sat Mar 28, 2009 0:02

Re: ebuilds not installing

Postby crisandbea » Mon Mar 30, 2009 7:40

ddfusion wrote:every ebuild i have tried to install fails.
I have followed these instructions http://wiki.sabayonlinux.org/index.php? ... ty_Ebuilds

could it be the ebuilds are no good or am i missing something?
could anyone please help me thro this?

thanks



can you post error????????
crisandbea
Old Dear Hen
 
Posts: 651
Joined: Tue Feb 12, 2008 11:36
Location: Bosco(SA)

Re: ebuilds not installing

Postby joost » Mon Mar 30, 2009 12:41

Did you do a minimal install for light computers?
In that case you should follow instructions on how to make portage work on POD release.

Anyway, more info needed.
joost
Sagely Hen
 
Posts: 2582
Joined: Fri Nov 17, 2006 12:11
Location: The Netherlands

Re: 3rd party ebuilds in local overlay not installing

Postby Fitzcarraldo » Mon Mar 30, 2009 13:51

I modified thread title to clarify topic, since OP is referring to a Wiki article specifically on 3rd party ebuilds in a local overlay. Presumably (s)he can merge ebuilds in main Portage tree and other overlays (sabayon overlay, for example).
User avatar
Fitzcarraldo
Sagely Hen
 
Posts: 7985
Joined: Sat Mar 10, 2007 5:40
Location: United Kingdom

Re: 3rd party ebuilds in local overlay not installing

Postby albfneto » Mon Mar 30, 2009 14:53

FitzCarraldo, i have in mind that even the user had copied the ebuild in the main portage directory, or in one overlay directory, instead of the local directory.... if copied properly, and make.conf adequate.... it will install normally....
although this is not so good,because causes confusion in the user's system... can be made,if specify version...
in a example:

" download the hypotetic version (888) of conary-888.ebuild
copied to:
/usr/portage/app-admin/conary
after

# cd /
# cd /usr/portage/app-admin/conary
# ebuild conary-888.ebuild manifest (or digest )

running "sudo emerge -av =/app-admin/conary-888 "


Normally it will install., no?
Is possible that the user had mistaken the category sub-directory, or mistaken to run the ebuild command?
ALBERTO FEDERMAN NETO
albfneto
[email protected]
Favorite Distros: Sabayon, Gentoo, Mageia and OpenSUSE
User avatar
albfneto
Sagely Hen
 
Posts: 1725
Joined: Fri Nov 16, 2007 1:15
Location: Ribeirão Preto City, São Paulo State, Brazil

Re: 3rd party ebuilds in local overlay not installing

Postby wolfden » Mon Mar 30, 2009 21:42

albfneto wrote:FitzCarraldo, i have in mind that even the user had copied the ebuild in the main portage directory, or in one overlay directory, instead of the local directory.... if copied properly, and make.conf adequate.... it will install normally....
although this is not so good,because causes confusion in the user's system... can be made,if specify version...
in a example:

" download the hypotetic version (888) of conary-888.ebuild
copied to:
/usr/portage/app-admin/conary
after

# cd /
# cd /usr/portage/app-admin/conary
# ebuild conary-888.ebuild manifest (or digest )

running "sudo emerge -av =/app-admin/conary-888 "


Normally it will install., no?
Is possible that the user had mistaken the category sub-directory, or mistaken to run the ebuild command?


without error message/build log, nobody knows what it could be, could be a setting in make.conf as far as we know
wolfden
Sharecropper
 
Posts: 9051
Joined: Sat Jan 14, 2006 0:55
Location: Midwest USA


Return to Portage|Emerge Package Managers

Who is online

Users browsing this forum: No registered users and 1 guest

cron