| Summary: | Support for a pre-compile pkg_config | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Kristian Benoit <kbenoit> |
| Component: | Core - Ebuild Support | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | enhancement | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
New feature (preconfig) to optionally run src_preconfig in packages providing such a function.
An example of it's use with busybox. Busybox patch to use preconfig |
||
Created attachment 63783 [details, diff]
New feature (preconfig) to optionally run src_preconfig in packages providing such a function.
It would be nice to enhance emerge so that packages that need preconfig be
preconfigured before any compilation is done. So the user get the interactive
stuff a the right when emerge start and not bother him at random stages.
Created attachment 63784 [details, diff]
An example of it's use with busybox.
This show how it can be used in with busybox which require such a
configuration.
busybox comes with defaults, it isnt a problem to use those defaults Comment on attachment 63784 [details, diff]
An example of it's use with busybox.
wrong patch
Created attachment 64354 [details, diff]
Busybox patch to use preconfig
Not sure about this one. There's so few packages that could use it. USE flags are (theoretically) designed specifically to prevent the need for it. additionally, requires inspecting the graph to ensure necessary deps for unpacking phase are there (can't configure it if you can't unpack it). This was discussed and decided on on the portage-dev ml: http://thread.gmane.org/gmane.linux.gentoo.portage.devel/2054/focus=2054 |
The actual solution is to to get the source, unpack, configure and copy the configuration file to a prespecified place in the filetree by hand so the ebuild could find it and use it. Reproducible: Always Steps to Reproduce: 1. emerge busybox Actual Results: It use a default config or the one found in /etc/busybox/${CHOST}/busybox*.config. Expected Results: Be able to request emerge to pop an optional interactive configuration tool before compilation when ebuild provide such a functionality.