Poky Project Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Tom Rini <tom_rini@mentor.com>
Cc: poky@yoctoproject.org
Subject: Re: Native vs not
Date: Mon, 14 Mar 2011 17:55:26 +0000	[thread overview]
Message-ID: <1300125326.30423.343.camel@rex> (raw)
In-Reply-To: <4D7E547A.5020906@mentor.com>

On Mon, 2011-03-14 at 10:46 -0700, Tom Rini wrote:
> On 03/14/2011 10:40 AM, Richard Purdie wrote:
> > On Mon, 2011-03-14 at 10:26 -0700, Tom Rini wrote:
> >> On 03/11/2011 05:10 PM, Khem Raj wrote:
> >>
> >>> I think having some buildhost/native packages (based on distro/version) trusted and assume provided or even
> >>> installed using the build host package management could be one approach
> >>> in modern distros I think we could use lot of host packages as is. or
> >>> may be trust all and keep a list of blacklisted packages for a given
> >>> distro might be something useful
> >>
> >> I've been thinking about this a bit and at least at the high level there
> >> is an argument for making it easy to opt out of a big class of host
> >> tools, on a modern distro and trade reprodicibility / reliability for
> >> faster initial build times.  And on the flip side, opt out of a bit more
> >> of our host tool dependencies.
> >
> > This is what ASSUME_PROVIDED is there for :)
> 
> Well yes.  But it'd be nice if we had a few helpers so you could say:
> ASSUME_PROVIDED += "${SCM_FETCH_TOOLS} ${DOCUMENTATION_GENERATION_TOOLS} 
> ..."
> and so forth.

We need to user to be very clearly aware of what they're adding IMO so
I'd prefer maybe just some commented out lines such as:

# Uncomment this if you want to use the system provided scm utilities
# instead of having the system build them
#ASSUME_PROVIDED += "git-native svn-native"

I'm actually thinking about a local.conf.sample.advanced file where we
list a load of things like this. This means we can keep
local.conf.sample simple (the things they probably *need* to look at)
yet still show users some of the other more advanced options.

Cheers,

Richard



  reply	other threads:[~2011-03-14 17:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-11 11:34 Native vs not Gary Thomas
2011-03-11 17:13 ` Richard Purdie
2011-03-11 17:20   ` Gary Thomas
2011-03-11 17:25     ` Tom Rini
2011-03-11 17:32       ` Gary Thomas
2011-03-12  0:10         ` Khem Raj
2011-03-14 17:26           ` Tom Rini
2011-03-14 17:40             ` Richard Purdie
2011-03-14 17:46               ` Tom Rini
2011-03-14 17:55                 ` Richard Purdie [this message]
2011-03-14 18:03                   ` Tom Rini
2011-03-14 18:26                     ` Gary Thomas

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=1300125326.30423.343.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=poky@yoctoproject.org \
    --cc=tom_rini@mentor.com \
    /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