All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Yocto discussion list <yocto@yoctoproject.org>
Subject: [OT?] some inconsistencies in listing required build software
Date: Tue, 17 Jun 2014 07:57:37 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1406170746340.30240@localhost> (raw)


  not sure if this is the right list (oe/poky/yocto?), but since it
involves yocto docs, i'll ask here.

  there seem to be some (admittedly minor) inconsistencies in both the
docs and code for checking the sanity of a build environment (i'm
basing this off the current yocto docs and the current poky master
branch).

  first, over at the QS guide:

http://www.yoctoproject.org/docs/latest/yocto-project-qs/yocto-project-qs.html

there are, of course, the list of required packages for the common
distros, and these lists refer to *packages* to be installed. this is
fine, but the wording suggests that the developer is responsible for
manually installing them, without mentioning that yocto itself will
help them out later with the sanity checking. i think that's useful to
know, but there's more.

  over in meta/conf/bitbake.conf, there is what i assume is the
default list of ASSUME_PROVIDED commands:

ASSUME_PROVIDED = "\
    bzip2-native \
    chrpath-native \
    git-native \
    grep-native \
    diffstat-native \
    patch-native \
    perl-native-runtime \
    python-native-runtime \
    tar-native \
    virtual/libintl-native \
    texinfo-native\
    "
# gzip-native should be listed above?

  so the first question is, given that the QS guide suggests gzip is a
*required* package (see fedora and centos package lists), why *isn't*
gzip part of ASSUME_PROVIDED above? it seems that the QS packages list
and the above should match, no?

  finally, over in meta/classes/sanity.bbclass, there's:

#
# Sanity check the users setup for common misconfigurations
#

SANITY_REQUIRED_UTILITIES ?= "patch diffstat makeinfo git bzip2 tar \
    gzip gawk chrpath wget cpio perl"

  silly question -- is this list supposed to represent the utilities
that must be on the machine *before* any OE processing is done?
because, again , there seems to be an inconsistency in that this seems
to require gzip, while ASSUME_PROVIDED doesn't mention it. it also
doesn't mention unzip, which the QS packages lists refer to as
required.

  none of this is a big deal, of course, but it would be nice if it
were consistent.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================


                 reply	other threads:[~2014-06-17 12:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LFD.2.11.1406170746340.30240@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.