| Summary: | Should be able to define Target Proxy settings and have them appear in images | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | brian avery <brian.avery> |
| Component: | configuration | Assignee: | Unassigned <unassigned> |
| Status: | RESOLVED OBSOLETE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium+ | CC: | bruce.ashfield, joshuagloe, randy.macleod, richard.purdie, ross.burton, stephano |
| Version: | 2.4 | ||
| Target Milestone: | 5.99 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
brian avery
2017-07-12 18:12:32 UTC
Adding Ross as likely to have a better strawman candidate,Bruce for docker tie in, joshua for interest/suggestions. dnf is another example of a sw package that needs custom proxy configuration. Indeed, this is something that would be needed by multiple applications (docker included). The first question that pops to mind for me, is: is there really a generic way to handle this ? i.e. isn't it fundamentally something that is both application and image specific ? i.e. you define something as you describe below in some sort of global namespace and it is up to recipes that need proxy settings to see those values, and then interpret them to what their particular needs are ? some sort of distro setting that recipes can use to trigger the writing of their proxy config. as far as i know, there's no generic way, but i like the idea of a distro setting as trigger, so the recipes know whether to write out the proxy files or not; and the ability to define the various (http/ftp/socks/...) proxies in my local.conf file. Long term I still believe that David Woodhouse's proposal for Fedora makes sense universally, but with s/networkmanager/connman/ for us. That is luckily an implementation detail and already implemented in connman, the non-trivial bit is making the world use libproxy. Propose a staged approach. This bug targets adding a mechanism, the environment as a bare minimum. Individual issues with apps are then handled on a case by case, patch by patch basis beyond this bug. Please provide an update for this. Will it make it into 2.5 M3? Bulk move from 4.99 or 0.00 to 5.99 Scope too large. |