Skip to contentSkip to conversation

ref-manual: bump tar and python min versions

PATCH New Tim Orling 1 participant 5 messages Apr 3, 2020

lore
Share & tools
lore

Tim Orling

author
#0 lore raw

PATCH 1/5 ref-manual: bump tar and python min versions

* tar min version is now 1.28
* python min version is now 3.5

---
 documentation/ref-manual/ref-system-requirements.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
documentation/ref-manual/ref-system-requirements.xml +2 -2
index e65ef6350..21cd79de0 100644
@@ -314,8 +314,8 @@
             Python:
             <itemizedlist>
                 <listitem><para>Git 1.8.3.1 or greater</para></listitem>
-                <listitem><para>tar 1.27 or greater</para></listitem>
-                <listitem><para>Python 3.4.0 or greater</para></listitem>
+                <listitem><para>tar 1.28 or greater</para></listitem>
+                <listitem><para>Python 3.5.0 or greater</para></listitem>
             </itemizedlist>
         </para>
 
Signature · 1 line
2.24.0
author
#1 lore raw

PATCH 2/5 ref-manual: fix debian-8 system reqs

jessie-backports is no longer supported, so python3-git and pylint3 are not installable via apt-get (or at least not without disabling security checks by using archive.debian.org)

Add note to use pip3 to install instead.

---
 .../ref-manual/ref-system-requirements.xml    | 32 ++++++++++++-------
 1 file changed, 21 insertions(+), 11 deletions(-)
documentation/ref-manual/ref-system-requirements.xml +21 -11
index 21cd79de0..6153117f1 100644
@@ -130,19 +130,29 @@
             <para>
                 The following list shows the required packages by function
                 given a supported Ubuntu or Debian Linux distribution:
-                <note>
-                    If your build system has the
-                    <filename>oss4-dev</filename> package installed, you
-                    might experience QEMU build failures due to the package
-                    installing its own custom
-                    <filename>/usr/include/linux/soundcard.h</filename> on
-                    the Debian system.
-                    If you run into this situation, either of the following
-                    solutions exist:
-                    <literallayout class='monospaced'>
+                <note><title>Notes</title>
+                    <itemizedlist>
+                        <listitem><para>
+                            If your build system has the
+                            <filename>oss4-dev</filename> package installed, you
+                            might experience QEMU build failures due to the package
+                            installing its own custom
+                            <filename>/usr/include/linux/soundcard.h</filename> on
+                            the Debian system.
+                            If you run into this situation, either of the following
+                            solutions exist:
+                            <literallayout class='monospaced'>
      $ sudo apt-get build-dep qemu
      $ sudo apt-get remove oss4-dev
-                    </literallayout>
+                            </literallayout>
+                        </para></listitem>
+                        <listitem><para>
+                            For Debian-8, <filename>python3-git</filename> and <filename>pylint3</filename> are no longer available via <filename>apt-get</filename>.
+                            <literallayout class='monospaced'>
+     $ sudo pip3 install GitPython pylint==1.9.5
+                            </literallayout>
+                        </para></listitem>
+                    </itemizedlist>
                  </note>
                 <itemizedlist>
                     <listitem><para><emphasis>Essentials:</emphasis>
Signature · 1 line
2.24.0
author
#2 lore raw

PATCH 3/5 ref-manual: add install-buildtools and -extended

In reply to Tim Orling

Add instructions to use 'install-buildtools' and
'buildtools-extended-tarball'.

Add gcc 5.0 requirement and call out how to
use above to prepare host development system.

---
 documentation/ref-manual/faq.xml              |   4 +-
 documentation/ref-manual/migration.xml        |   6 +-
 .../ref-manual/ref-system-requirements.xml    | 127 ++++++++++++++++--
 3 files changed, 120 insertions(+), 17 deletions(-)
documentation/ref-manual/faq.xml +2 -2
index 49ff86261..d94cb32a8 100644
@@ -33,7 +33,7 @@
             <para id='faq-not-meeting-requirements'>
                 My development system does not meet the
                 required Git, tar, and Python versions.
-                In particular, I do not have Python 3.4.0 or greater.
+                In particular, I do not have Python 3.5.0 or greater.
                 Can I still use the Yocto Project?
             </para>
         </question>
@@ -43,7 +43,7 @@
                 system a couple different ways (i.e. building a tarball or
                 downloading a tarball).
                 See the
-                "<link linkend='required-git-tar-and-python-versions'>Required Git, tar, and Python Versions</link>"
+                "<link linkend='required-git-tar-python-and-gcc-versions'>Required Git, tar, Python and gcc Versions</link>"
                 section for steps on how to update your build tools.
             </para>
         </answer>
documentation/ref-manual/migration.xml +3 -3
index 80a6acc95..03efc7be2 100644
@@ -680,7 +680,7 @@
 
         <para>
             For more information on this requirement, see the
-            "<link linkend='required-git-tar-and-python-versions'>Required Git, tar, and Python Versions</link>"
+            "<link linkend='required-git-tar-python-and-gcc-versions'>Required Git, tar, Python and gcc Versions</link>"
             section.
         </para>
     </section>
@@ -1754,7 +1754,7 @@
             Git that meets this requirement, you can use the
             <filename>buildtools-tarball</filename> that does.
             See the
-            "<link linkend='required-git-tar-and-python-versions'>Required Git, tar, and Python Versions</link>"
+            "<link linkend='required-git-tar-python-and-gcc-versions'>Required Git, tar, Python and gcc Versions</link>"
             section for more information.
         </para>
     </section>
@@ -3215,7 +3215,7 @@
                     recent version, you can install the buildtools, which
                     will provide it.
                     See the
-                    "<link linkend='required-git-tar-and-python-versions'>Required Git, tar, and Python Versions</link>"
+                    "<link linkend='required-git-tar-python-and-gcc-versions'>Required Git, tar, Python and gcc Versions</link>"
                     section for more information on the buildtools tarball.
                     </para></listitem>
                 <listitem><para>
documentation/ref-manual/ref-system-requirements.xml +115 -12

200 lines not on this page · raw message

Signature · 1 line
2.24.0
author
#3 lore raw

PATCH 4/5 dev-manual: buildtools versions and changes

In reply to Tim Orling

Bump tar, Python versions and add new gcc requirement.

Update reference from 'required-git-tar-and-python-versions' to 'required-git-tar-python-and-gcc-versions'

---
 documentation/dev-manual/dev-manual-start.xml | 13 ++++++++-----
 1 file changed, 8 insertions(+), 5 deletions(-)
documentation/dev-manual/dev-manual-start.xml +8 -5
index a151ba61c..8cb5631f0 100644
@@ -467,23 +467,26 @@
                     <emphasis>Meet Minimal Version Requirements:</emphasis>
                     The OpenEmbedded build system should be able to run on any
                     modern distribution that has the following versions for
-                    Git, tar, and Python.
+                    Git, tar, Python and gcc.
                     <itemizedlist>
                         <listitem><para>
                             Git 1.8.3.1 or greater
                             </para></listitem>
                         <listitem><para>
-                            tar 1.27 or greater
+                            tar 1.28 or greater
                             </para></listitem>
                         <listitem><para>
-                            Python 3.4.0 or greater.
-                            </para></listitem>
+                            Python 3.5.0 or greater.
+                        </para></listitem>
+                        <listitem><para>
+                            gcc 5.0 or greater.
+                        </para></listitem>
                     </itemizedlist>
                     If your build host does not meet any of these three listed
                     version requirements, you can take steps to prepare the
                     system so that you can still use the Yocto Project.
                     See the
-                    "<ulink url='&YOCTO_DOCS_REF_URL;#required-git-tar-and-python-versions'>Required Git, tar, and Python Versions</ulink>"
+                    "<ulink url='&YOCTO_DOCS_REF_URL;#required-git-tar-python-and-gcc-versions'>Required Git, tar, Python and gcc Versions</ulink>"
                     section in the Yocto Project Reference Manual for
                     information.
                     </para></listitem>
Signature · 1 line
2.24.0
author
#4 lore raw

PATCH 5/5 brief-yoctoprojectqs: buildtools changes

In reply to Tim Orling

Bump tar, Python versions and add new gcc requirement.

Update reference from 'required-git-tar-and-python-versions' to 'required-git-tar-python-and-gcc-versions'

---
 .../brief-yoctoprojectqs/brief-yoctoprojectqs.xml     | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)
documentation/brief-yoctoprojectqs/brief-yoctoprojectqs.xml +7 -4
index 9b976014a..3c83afd46 100644
@@ -107,17 +107,20 @@
                             Git 1.8.3.1 or greater
                             </para></listitem>
                         <listitem><para>
-                            tar 1.27 or greater
+                            tar 1.28 or greater
                             </para></listitem>
                         <listitem><para>
-                            Python 3.4.0 or greater.
-                            </para></listitem>
+                            Python 3.5.0 or greater.
+                        </para></listitem>
+                        <listitem><para>
+                            gcc 5.0 or greater.
+                        </para></listitem>
                     </itemizedlist>
                     If your build host does not meet any of these three listed
                     version requirements, you can take steps to prepare the
                     system so that you can still use the Yocto Project.
                     See the
-                    "<ulink url='&YOCTO_DOCS_REF_URL;#required-git-tar-and-python-versions'>Required Git, tar, and Python Versions</ulink>"
+                    "<ulink url='&YOCTO_DOCS_REF_URL;#required-git-tar-python-and-gcc-versions'>Required Git, tar, Python and gcc Versions</ulink>"
                     section in the Yocto Project Reference Manual for information.
                     </para></listitem>
             </itemizedlist>
Signature · 1 line
2.24.0