From: Brad Bishop <bradleyb@fuzziesquirrel.com>
To: Patrick Venture <venture@google.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Host-side tools
Date: Mon, 11 Feb 2019 13:50:46 -0500 [thread overview]
Message-ID: <20190211185046.2lisomjnecvrd7eh@thinkpad.dyn.fuzziesquirrel.com> (raw)
In-Reply-To: <CAO=notwr7mZQ_ww_z7Vn94SrvmGZu6v+KK-LwujvSmK4v3ut0g@mail.gmail.com>
On Mon, Feb 11, 2019 at 08:03:17AM -0800, Patrick Venture wrote:
>Brad,
>
>It's my understanding that host-side tools that cooperate with bmc-side
>tools should be in the same repo,
Is this something I said at some point? Where is this coming from?
>hence why the host-side blobs stuff is in phosphor-ipmi-flash.
>However, if I add any dependencies to the configuration for the
>BMC-side, those get in the way of configuring for the host-side. Would
>it not make sense to sometimes have it split? And if so, I would like
>to propose creating two repos, a blobs library host-side, and a flash
>tool host-side repo, so those can be neatly split and not have anything
>in their configuration file that's really bmc-side specific, like
>ipmid, or phosphor-dbus-interface, or something.
I can make a repo if you would like. Just let me know what you would
like it called.
That said, I think you can also probably do this in the same repo, if
you wanted, by having different build targets - it might not make any
sense to try and build both applications with a single invocation of
configure - as you point out, they are being "configured" for vastly
different runtime environments.
next prev parent reply other threads:[~2019-02-11 18:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 16:03 Host-side tools Patrick Venture
2019-02-11 18:50 ` Brad Bishop [this message]
2019-02-11 19:48 ` William Kennington
2019-02-11 22:58 ` Patrick Venture
2019-02-11 23:07 ` Patrick Venture
2019-02-12 17:11 ` Patrick Venture
2019-02-12 21:33 ` Vijay Khemka
2019-02-13 20:23 ` Patrick Venture
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=20190211185046.2lisomjnecvrd7eh@thinkpad.dyn.fuzziesquirrel.com \
--to=bradleyb@fuzziesquirrel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=venture@google.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 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.