Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: on current linux distros, what are potential candidates for ASSUME_PROVIDED?
Date: Wed, 25 Feb 2015 03:25:30 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.11.1502250320080.23957@localhost> (raw)


  for the sake of reducing build time in the classroom, what are some
of the potential (and relatively safe) candidates to add to
ASSUME_PROVIDED for a build from scratch?

  i do recall that, once one starts adding more native packages to
that variable, QA becomes an issue but, given a modern distro such as
fedora 21, surely there are quite a number of packages that are safe
to add.

  the first thing i always add is "subversion-native" (since i don't
think subversion is even *used* in a core-image-minimal build, but i
could be wrong). i'm looking through all the -native builds and can
see other possible candidates i'm going to try -- open to suggestions
as to what should be safe, and i'll test it out.

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:[~2015-02-25  8:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-25  8:25 Robert P. J. Day [this message]
2015-02-25  8:36 ` on current linux distros, what are potential candidates for ASSUME_PROVIDED? Richard Purdie
2015-02-25  8:41   ` Robert P. J. Day
2015-02-26 19:03     ` Stephen Arnold

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.1502250320080.23957@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox