Summary: | package configuration files | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Geert Bevin <gbevin> |
Component: | Core - Ebuild Support | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | aholler, azarah, blizzy-keyword-gentoo_bugs2.a8a736, carpaski, clmason, g2boojum, lordvan, sascha-gentoo-bugzilla, spider, yggsdrasil |
Priority: | High | Keywords: | InVCS |
Version: | 2.0 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Geert Bevin
2002-01-31 14:17:33 UTC
*** Bug 461 has been marked as a duplicate of this bug. *** I'll add this soon. We desperately need it. *** Bug 1887 has been marked as a duplicate of this bug. *** neat.. i think! :) sounds like another huge round of cleanups. but still.. neat! This sounds good, yes. While on a similar subject, is there a way to keep a variable assignment between the different parts of an ebuild? ie, set a variable in src_install and get it again in pkg_config or in the new set? this would be good for cases like "check the files installed "there" and perform an action on them. Sure, this could be handled by manually checking files and typing down names, but this makes for a lot of errors by ebuild creators. For keeping vars: I guess you could do env>${TEMPDIR}/vars and . ${TEMPDIR}/vars in the functions? Are this stil in the pipeline, or something else planned ? Still in the pipeline. (At least something like it) nice suggestion from 10801 ... `emerge --config <pkg>` *** Bug 10801 has been marked as a duplicate of this bug. *** Tiz an enhancement, so marking it as such. emerge --config available in 2.0.51.21 Fixed on or before 2.0.51.22-r1 Looking through the batch of bugs, I'm not sure that some of these are actually fixed in stable. Others, the requirements have possibly changed after the initial fix was committed. If you think this bug has been closed incorrectly, please reopen or ask that it be reopened. |