phosphor: use standard proxy settings for phosphor-webui recipe

The current phosphor-webui compile stage needs to connect to the npm
registry. In build environments that use a proxy (specified by the
`http_proxy`) setting, this fails.

Although the current recipe provides proxy arguments through the
HTTP_PROXY environment variable, not many other download tools use this
(wget and curl do not).

Since the lower-case version needs to be set anyway (for wget), use that
instead of requiring both http_proxy and HTTP_PROXY.

Tested: phosphor-webui's do_compile target works with only
  http{,s}_proxy set

Fixes: https://github.com/openbmc/meta-phosphor/issues/14
Change-Id: I058134f458e95b37384f8615163a2c60f882918f
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
1 file changed
tree: 1c234bb60e76684c251f389618d6c0d314d688fe
  1. aspeed-layer/
  2. classes/
  3. conf/
  4. nuvoton-layer/
  5. recipes-connectivity/
  6. recipes-core/
  7. recipes-devtools/
  8. recipes-extended/
  9. recipes-graphics/
  10. recipes-phosphor/
  11. recipes-protocols/
  12. recipes-support/
  13. recipes-textproc/
  14. COPYING.apache-2.0
  15. COPYING.MIT
  16. LICENSE
  17. MAINTAINERS
  18. README.md
  19. recipes.txt
README.md

OpenBMC

meta-phosphor is the OpenBMC layer. This layer should be included for all OpenBMC systems. The OpenBMC layer contains content which is shared between all OpenBMC systems.