summaryrefslogtreecommitdiffstats
path: root/meta-yocto/conf/site.conf.sample
Commit message (Collapse)AuthorAgeFilesLines
* meta-yocto: Rename to meta-poky to better match its purposeRichard Purdie2016-02-281-31/+0
| | | | | | | | | | | | | | | | | "poky" is the reference distribution for the Yocto Project. This renames the layer within the meta-yocto repository to meta-poky, better matching what that layer contains. A layer.conf file is left behind as this is the only way which allows existing builds to migrate safely to the new name. It will be removed at some future point. This change requires the corresponding OE-Core change to handle the migration and the changes to the infrastructure to support this. (From meta-yocto rev: d0c88df2e14672fca4ebbde93c5efbcd0e4fa9b6) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* local.conf.sample: use ?= to assign BB_ENV_EXTRAWHITE variablesJesse Zhang2013-06-171-3/+3
| | | | | | | | | | Use ?= so that the BB_ENV_EXTRAWHITE variables can be overridden from the environment. [YOCTO #4367] Signed-off-by: Jesse Zhang <sen.zhang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-yocto: Document new oe-git-proxy in site.conf.sampleDarren Hart2013-02-111-26/+9
| | | | | | | | | | | | | The new oe-git-proxy.sh should address all git proxying needs. Document its usage in meta-yocto/conf/site.conf.sample and remove references to the old mechanisms. V2: Separate out the meta-yocto changes from the oe-core changes (From meta-yocto rev: 4be5040a4d0b0fee0118ce31b233c666b8708b6a) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* site.conf.sample: Fix broken SOCKS proxy setup and configurationInaky Perez-Gonzalez2012-03-011-4/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | SOCKS proxy specification with git was using conflicting methods and thus was failing when mixed SOCKS needs were in place (requiring no proxy for some hosts and proxy for the rest) - GIT_PROXY_COMMAND is an environment variable GIT uses to OVERRIDE all proxy configuration in ~/.gitconfig or any other gitconfig. By using it to configure, it was breaking havoc on site git configuration or the one generated by bitbake in tmp/. Renamed to OE_GIT_PROXY_COMMAND in meta/conf/site.conf.sample (with a doc tidbit on the name chosen), meta/classes/base.bbclass. - The gitconfig generated by bitbake was wrong. There was a typo error (gitproxy vs gitProxy), thus all lines were being ignored. Fixed in meta/classes/base.bbclass. - The gitconfig generated was being placed in ${STAGING_DIR_NATIVE}/usr/etc/gitconfig; git was looking for it in ${STAGING_DIR_NATIVE}/etc/gitconfig. Fixed that in meta/classes/base.bbclass, at the same time creating a GIT_CONFIG_PATH variable, since it is also referenced in generate_git_config() and have all instances refer to that. (From OE-Core rev: e579eb7f33462258c8e82a0936d970593614840d) Signed-off-by: Inaky Perez-Gonzalez <inaky.perez-gonzalez@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-yocto: Catch up with OE-Core renamingRichard Purdie2011-04-201-3/+3
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-yocto: Move files inappropriate to OE-Core from metaRichard Purdie2011-03-031-0/+40
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>