Summary: | need to tell how to specify a dependancy that must have been built a certain way and how to build it | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Aaron Peterson <alpeterson> |
Component: | Documentation | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Aaron Peterson
2003-05-02 08:43:23 UTC
I ran into this problem with my Overnet Core Controller ebuild (its floating arround on the forums somewhere..)
anyway... yeah i think it was glib1.2 and glib2 that was causing the problems... I had to edit the ebuild and re emerge the other thing...
I suppose one could just "merge" the ebuilds together... compile the requirement, then compile the goodie... then somehow emerge the requirement again with it's normal settings...
This should be specified... maybe like this
Depends{
>=foolib3.1
>=barlib2.3.1:glib[glib2]
to say that it has to be built with glib2 instead of 1.2 or something..
use a colon or some other symbol in the use flags...
then portage should know to re emerge the file after its done...
and the glib package would have to accept being passed a build value...
I'm tired... and my system is... not as broken as it has been... (my girlfriend is going to be mad at me... again... for attempting to fix my gentoo box)
|