From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2 1/1] buildtools-tarball: restore missing git tools
Date: Sat, 06 Dec 2014 16:50:15 +0000 [thread overview]
Message-ID: <1417884615.5102.27.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAP9ODKrs_-Ed7J3ra2u1nVvC9QMkToNpBsefvufJSepaZB0O2g@mail.gmail.com>
On Sat, 2014-12-06 at 14:10 -0200, Otavio Salvador wrote:
> On Sat, Dec 6, 2014 at 12:37 PM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > At some point you have to depend on the host system, be it perl, sh or
> > other things. The exact line should be configurable, Paul is simply
> > adding a mechanism here that allows us to control that. He's needed a
> > default and I think perl is API stable enough that we should be ok here.
>
> I understand but the provided mechanism is ugly and hackish.
>
> Maybe a mechanism like 'ASSUME_PROVIDED' could be made and use for
> this use-case. A dummy package looks like a workaround.
The mechanism needs to work at the package manager level, not at bitbake
since that is where the problem is. I'm not aware of mechanisms in any
of the package managers, let alone one common to all of them.
As Paul said, better ideas more than welcome.
Cheers,
Richard
next prev parent reply other threads:[~2014-12-06 16:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-05 18:09 [PATCH v2 0/1] Fix buildtools after git-perltools split Paul Eggleton
2014-12-05 18:09 ` [PATCH v2 1/1] buildtools-tarball: restore missing git tools Paul Eggleton
2014-12-05 18:30 ` Otavio Salvador
2014-12-06 1:39 ` Paul Eggleton
2014-12-06 13:01 ` Otavio Salvador
2014-12-06 13:40 ` Peter A. Bigot
2014-12-06 17:14 ` Paul Eggleton
2014-12-06 14:37 ` Richard Purdie
2014-12-06 16:10 ` Otavio Salvador
2014-12-06 16:50 ` Richard Purdie [this message]
2014-12-06 17:08 ` Paul Eggleton
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=1417884615.5102.27.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
--cc=paul.eggleton@linux.intel.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