3rd party ebuilds in local overlay not installing

[ddfusion]

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

[crisandbea]

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????????

[joost]

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.

[Fitzcarraldo]

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).

[albfneto]

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?

[wolfden]

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