<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/meta-yocto/conf/site.conf.sample, branch thud</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=thud</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=thud'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2016-02-28T11:31:17+00:00</updated>
<entry>
<title>meta-yocto: Rename to meta-poky to better match its purpose</title>
<updated>2016-02-28T11:31:17+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2016-02-16T16:42:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=9d5483c37523ff3d334c98cafb848282b54962cd'/>
<id>urn:sha1:9d5483c37523ff3d334c98cafb848282b54962cd</id>
<content type='text'>
"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 &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>local.conf.sample: use ?= to assign BB_ENV_EXTRAWHITE variables</title>
<updated>2013-06-17T15:27:59+00:00</updated>
<author>
<name>Jesse Zhang</name>
<email>sen.zhang@windriver.com</email>
</author>
<published>2013-06-06T06:20:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=7f58f4c5f4e0a49b002124636d1f1c568d17bbbc'/>
<id>urn:sha1:7f58f4c5f4e0a49b002124636d1f1c568d17bbbc</id>
<content type='text'>
Use ?= so that the BB_ENV_EXTRAWHITE variables can be overridden from
the environment.

[YOCTO #4367]

Signed-off-by: Jesse Zhang &lt;sen.zhang@windriver.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>meta-yocto: Document new oe-git-proxy in site.conf.sample</title>
<updated>2013-02-11T22:54:04+00:00</updated>
<author>
<name>Darren Hart</name>
<email>dvhart@linux.intel.com</email>
</author>
<published>2013-02-08T22:27:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=54728735d67b567cdb067f793490ad15c448c828'/>
<id>urn:sha1:54728735d67b567cdb067f793490ad15c448c828</id>
<content type='text'>
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 &lt;dvhart@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>site.conf.sample: Fix broken SOCKS proxy setup and configuration</title>
<updated>2012-03-01T16:35:53+00:00</updated>
<author>
<name>Inaky Perez-Gonzalez</name>
<email>inaky.perez-gonzalez@intel.com</email>
</author>
<published>2012-03-01T09:44:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=7bb36e5da0d28404d7b272135045cdb5cb160472'/>
<id>urn:sha1:7bb36e5da0d28404d7b272135045cdb5cb160472</id>
<content type='text'>
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 &lt;inaky.perez-gonzalez@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>meta-yocto: Catch up with OE-Core renaming</title>
<updated>2011-04-20T23:29:33+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2011-04-20T23:14:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=765d380e33f485a5ba9f10adabbb88440f9eaf07'/>
<id>urn:sha1:765d380e33f485a5ba9f10adabbb88440f9eaf07</id>
<content type='text'>
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>meta-yocto: Move files inappropriate to OE-Core from meta</title>
<updated>2011-03-03T23:53:32+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2011-03-03T23:53:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=b0dec83e8c17d884323d58bb8d56c7ab6afa7ead'/>
<id>urn:sha1:b0dec83e8c17d884323d58bb8d56c7ab6afa7ead</id>
<content type='text'>
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
