diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2014-06-16 15:28:16 +0300 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2014-06-18 10:30:49 +0100 |
commit | 5a143d854f74dd089f245abd548aefe045b13521 (patch) | |
tree | f15c1fca8a6cfd6dd972c3bd99cb1e90edabc321 /documentation/ref-manual/faq.xml | |
parent | f82569f762b07a8fb50da62d23d756ceaff63ea4 (diff) | |
download | poky-5a143d854f74dd089f245abd548aefe045b13521.tar.gz |
ref-manual: Edits to the FAQ entry on getting source and firewalls.
I added a note at the end of the section to point to a wiki page
with more information.
(From yocto-docs rev: ba310c34844e9e496d7ff1164691930d4f330f93)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/ref-manual/faq.xml')
-rw-r--r-- | documentation/ref-manual/faq.xml | 91 |
1 files changed, 48 insertions, 43 deletions
diff --git a/documentation/ref-manual/faq.xml b/documentation/ref-manual/faq.xml index 035011f342..bc147ce70a 100644 --- a/documentation/ref-manual/faq.xml +++ b/documentation/ref-manual/faq.xml | |||
@@ -594,56 +594,61 @@ | |||
594 | <literallayout class='monospaced'> | 594 | <literallayout class='monospaced'> |
595 | BB_NO_NETWORK = "1" | 595 | BB_NO_NETWORK = "1" |
596 | </literallayout> | 596 | </literallayout> |
597 | This statement tells BitBake to issue an error instead of | 597 | This statement tells BitBake to issue an error instead of |
598 | trying to access the Internet. | 598 | trying to access the Internet. |
599 | This technique is useful if you want to ensure code builds | 599 | This technique is useful if you want to ensure code builds |
600 | only from local sources. | 600 | only from local sources. |
601 | </para> | 601 | </para> |
602 | <para> | 602 | <para> |
603 | Here is another technique: | 603 | Here is another technique: |
604 | <literallayout class='monospaced'> | 604 | <literallayout class='monospaced'> |
605 | BB_FETCH_PREMIRRORONLY = "1" | 605 | BB_FETCH_PREMIRRORONLY = "1" |
606 | </literallayout> | 606 | </literallayout> |
607 | This statement limits the build system to pulling source | 607 | This statement limits the build system to pulling source |
608 | from the <filename>PREMIRRORS</filename> only. | 608 | from the <filename>PREMIRRORS</filename> only. |
609 | Again, this technique is useful for reproducing builds. | 609 | Again, this technique is useful for reproducing builds. |
610 | </para> | 610 | </para> |
611 | <para> | 611 | <para> |
612 | Here is another technique: | 612 | Here is another technique: |
613 | <literallayout class='monospaced'> | 613 | <literallayout class='monospaced'> |
614 | BB_GENERATE_MIRROR_TARBALLS = "1" | 614 | BB_GENERATE_MIRROR_TARBALLS = "1" |
615 | </literallayout> | 615 | </literallayout> |
616 | This statement tells the build system to generate mirror | 616 | This statement tells the build system to generate mirror |
617 | tarballs. | 617 | tarballs. |
618 | This technique is useful if you want to create a mirror server. | 618 | This technique is useful if you want to create a mirror server. |
619 | If not, however, the technique can simply waste time during | 619 | If not, however, the technique can simply waste time during |
620 | the build. | 620 | the build. |
621 | </para> | 621 | </para> |
622 | <para> | 622 | <para> |
623 | Finally, consider an example where you are behind an | 623 | Finally, consider an example where you are behind an |
624 | HTTP-only firewall. | 624 | HTTP-only firewall. |
625 | You could make the following changes to the | 625 | You could make the following changes to the |
626 | <filename>local.conf</filename> configuration file as long as | 626 | <filename>local.conf</filename> configuration file as long as |
627 | the <filename>PREMIRRORS</filename> server is current: | 627 | the <filename>PREMIRRORS</filename> server is current: |
628 | <literallayout class='monospaced'> | 628 | <literallayout class='monospaced'> |
629 | PREMIRRORS_prepend = "\ | 629 | PREMIRRORS_prepend = "\ |
630 | ftp://.*/.* http://www.yoctoproject.org/sources/ \n \ | 630 | ftp://.*/.* http://www.yoctoproject.org/sources/ \n \ |
631 | http://.*/.* http://www.yoctoproject.org/sources/ \n \ | 631 | http://.*/.* http://www.yoctoproject.org/sources/ \n \ |
632 | https://.*/.* http://www.yoctoproject.org/sources/ \n" | 632 | https://.*/.* http://www.yoctoproject.org/sources/ \n" |
633 | BB_FETCH_PREMIRRORONLY = "1" | 633 | BB_FETCH_PREMIRRORONLY = "1" |
634 | </literallayout> | 634 | </literallayout> |
635 | These changes would cause the build system to successfully | 635 | These changes would cause the build system to successfully |
636 | fetch source over HTTP and any network accesses to anything | 636 | fetch source over HTTP and any network accesses to anything |
637 | other than the <filename>PREMIRRORS</filename> would fail. | 637 | other than the <filename>PREMIRRORS</filename> would fail. |
638 | </para> | 638 | </para> |
639 | <para> | 639 | <para> |
640 | The build system also honors the standard shell environment | 640 | The build system also honors the standard shell environment |
641 | variables <filename>http_proxy</filename>, | 641 | variables <filename>http_proxy</filename>, |
642 | <filename>ftp_proxy</filename>, | 642 | <filename>ftp_proxy</filename>, |
643 | <filename>https_proxy</filename>, and | 643 | <filename>https_proxy</filename>, and |
644 | <filename>all_proxy</filename> to redirect requests through | 644 | <filename>all_proxy</filename> to redirect requests through |
645 | proxy servers. | 645 | proxy servers. |
646 | </para> | 646 | </para> |
647 | <note> | ||
648 | You can find more information on the | ||
649 | "<ulink url='&YOCTO_WIKI_URL;/wiki/Working_Behind_a_Network_Proxy'>Working Behind a Network Proxy</ulink>" | ||
650 | Wiki page. | ||
651 | </note> | ||
647 | </answer> | 652 | </answer> |
648 | </qandaentry> | 653 | </qandaentry> |
649 | 654 | ||