All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Bishop <bradleyb@fuzziesquirrel.com>
To: Patrick Venture <venture@google.com>
Cc: Ratan Gupta <ratagupt@linux.vnet.ibm.com>,
	Andrew Jeffery <andrew@aj.id.au>,
	Ratan K Gupta <ratagupt@in.ibm.com>,
	OpenBMC Maillist <openbmc@lists.ozlabs.org>,
	"Tanous, Ed" <ed.tanous@intel.com>
Subject: Re: Sdbusplus-based Shared Library
Date: Wed, 28 Mar 2018 21:39:54 -0400	[thread overview]
Message-ID: <ED94F738-2C50-416D-826B-82BE0D1B0E94@fuzziesquirrel.com> (raw)
In-Reply-To: <CAO=notyvGn_nO1KgffBgukXy7hFt1VHnop26HpgJjJELeJMnow@mail.gmail.com>


> On Mar 27, 2018, at 11:43 AM, Patrick Venture <venture@google.com> wrote:
> 
> Brad,
> 
> If you create a repository - phosphor-sdbus-utils or
> phosphor-sdbusplus-utils or something like that, I'll put together a
> starter pack on this and submit for review.

May I suggest

https://github.com/openbmc/phosphor-dbus-monitor/tree/master/src/sdevent

as a possibility for drawing ideas?  :-)

> 
> Patrick

Thanks Patrick! will do but I’d like to get a bit more clarity/discussion
on what the content of this new repo will be.

So today we have sdbusplus built around the sd-bus folder in libsystemd.

Do we envision something like separate repos for:

sdeventplus - wrappers for the sd-event folder in libsystemd
sddeviceplus - wrappers for the sd-device folder in libsystemd
…etc

Or should we just try and have a single c++ wrapper repository for all of
libsystemd?  In that case should we simply rename sdbusplus to libsystemdpp
and start putting more code in it?

-brad

  reply	other threads:[~2018-03-29  1:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-19 17:11 Sdbusplus-based Shared Library Patrick Venture
2018-03-19 18:24 ` Tanous, Ed
2018-03-19 19:33   ` Patrick Venture
2018-03-20  2:32     ` Lei YU
2018-03-20  5:39     ` Tanous, Ed
2018-03-27  5:47     ` Andrew Jeffery
2018-03-27  6:04       ` Ratan Gupta
2018-03-27 15:43         ` Patrick Venture
2018-03-29  1:39           ` Brad Bishop [this message]
2018-03-29  3:25             ` Patrick Venture
2018-03-29  3:43               ` Brad Bishop
2018-07-18  8:36                 ` Lei YU
2018-03-20  6:36 ` Deepak Kodihalli
2018-07-18 11:34 ` vishwa
2018-07-18 13:53   ` Thomaiyar, Richard Marian

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=ED94F738-2C50-416D-826B-82BE0D1B0E94@fuzziesquirrel.com \
    --to=bradleyb@fuzziesquirrel.com \
    --cc=andrew@aj.id.au \
    --cc=ed.tanous@intel.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=ratagupt@in.ibm.com \
    --cc=ratagupt@linux.vnet.ibm.com \
    --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.