Summary: | env-update not appending LD_LIBRARY_PATH ? | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Stefan Janecek <stefan.janecek> |
Component: | [OLD] Core system | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Stefan Janecek
2005-04-26 07:30:07 UTC
Found it, portage.env_update only puts : in paths that are in special keys. colon_separated = [ "ADA_INCLUDE_PATH", "ADA_OBJECTS_PATH", "LDPATH", "MANPATH", "PATH", "PRELINK_PATH", "PRELINK_PATH_MASK", "PYTHON_PATH" ] # process PATH, CLASSPATH, LDPATH for myspec in specials.keys(): if myconfig.has_key(myspec): if myspec in colon_separated: specials[myspec].extend(string.split(va$ else: specials[myspec].append(varexpand(mycon$ del myconfig[myspec] # process all other variables for myenv in myconfig.keys(): env[myenv]=varexpand(myconfig[myenv]) since LD_LIBRARY_PATH isn't in color_seperated, no colons get put in and env only picks up the latest entry, not sure if this is a bug or a feature though...portage dudes? :) Er, there are times when nano sucks, and now is one of them ;) sorry about the $ :0 i'd say use LDPATH not LD_LIBRARY_PATH ... LD_LIBRARY_PATH shouldnt really be abused in this manor ... This is a WONTFIX then? Or are there ebuilds in the tree that use LD_LIBRARY_PATH? i dont know of any ebuilds that do and if they exist, they're broken imo i say this is a WONTFIX ... Agreed. |