poky.ent: Removed "python3-expect" package from 3 distros.
Fixes [YOCTO #11310] After a bit of deliberation.. it was decided that "python3-expect" is not needed in the Debian, Fedora, and OpenSUSE distros as an essential package. They are gone. (From yocto-docs rev: 07fcb23a03122e5f4f9bb2a32e585d9cba7d5d93) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
3db3344859
commit
def638ebd6
|
@ -61,15 +61,15 @@
|
|||
<!ENTITY OE_INIT_PATH "&YOCTO_POKY;/oe-init-build-env">
|
||||
<!ENTITY OE_INIT_FILE "oe-init-build-env">
|
||||
<!ENTITY UBUNTU_HOST_PACKAGES_ESSENTIAL "gawk wget git-core diffstat unzip texinfo gcc-multilib \
|
||||
build-essential chrpath socat cpio python python3 python3-pip python3-expect \
|
||||
build-essential chrpath socat cpio python python3 python3-pip \
|
||||
xz which">
|
||||
<!ENTITY FEDORA_HOST_PACKAGES_ESSENTIAL "gawk make wget tar bzip2 gzip python3 unzip perl patch \
|
||||
diffutils diffstat git cpp gcc gcc-c++ glibc-devel texinfo chrpath \
|
||||
ccache perl-Data-Dumper perl-Text-ParseWords perl-Thread-Queue perl-bignum socat \
|
||||
findutils which file cpio python python3-pip python3-expect xz which">
|
||||
findutils which file cpio python python3-pip xz which">
|
||||
<!ENTITY OPENSUSE_HOST_PACKAGES_ESSENTIAL "python gcc gcc-c++ git chrpath make wget python-xml \
|
||||
diffstat makeinfo python-curses patch socat python3 python3-curses tar python3-pip \
|
||||
python3-expect xz which">
|
||||
xz which">
|
||||
<!ENTITY CENTOS_HOST_PACKAGES_ESSENTIAL "-y epel-release
|
||||
$ sudo yum makecache
|
||||
$ sudo yum install gawk make wget tar bzip2 gzip python unzip perl patch \
|
||||
|
|
|
@ -3970,11 +3970,17 @@ $ runqemu qemux86-64 tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64.
|
|||
The Open-Embedded build system now uses one sysroot per
|
||||
recipe to resolve long-standing issues with configuration
|
||||
script auto-detection of undeclared dependencies.
|
||||
Consequently, you must explicitely declare all build-time
|
||||
Consequently, you must explicitly declare all build-time
|
||||
dependencies for your recipe.
|
||||
If you do not declare these dependencies, they are not
|
||||
populated into the sysroot for the recipe.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
You can find information on how this works in the
|
||||
<link linkend='ref-classes-staging'><filename>staging</filename></link>
|
||||
class.
|
||||
</para>
|
||||
</section>
|
||||
|
||||
<section id='migration-2.3-path-variable'>
|
||||
|
|
Loading…
Reference in New Issue