From: Mike Gilbert <floppym@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Re: rfc: status of OpenRC's public API
Date: Wed, 25 Sep 2013 16:27:42 -0400 [thread overview]
Message-ID: <CAJ0EP41RySjREWiBmDVaJA302-PKs8adRV_yQ1N76B_Zinyq6A@mail.gmail.com> (raw)
In-Reply-To: <20130925200409.GB14936@linux1>
On Wed, Sep 25, 2013 at 4:04 PM, William Hubbs <williamh@gentoo.org> wrote:
> On Tue, Sep 24, 2013 at 02:22:02PM -0400, Ian Stakenvicius wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>>
>> On 24/09/13 02:15 PM, William Hubbs wrote:
>> > On Sat, Sep 21, 2013 at 03:21:07PM -0400, Ian Stakenvicius wrote:
>> >> Out of curiosity, what is the reasoning behind making these libs
>> >> private?
>> >
>> > Well, the thought has changed slightly. librc can't be made
>> > private currently because of openrc-settingsd. libeinfo, on the
>> > other hand, does not have any known consumers, so there is no
>> > reason to keep it as a library.
>>
>> That doesn't answer my question, though; yes at this point there's no
>> reason to keep it public, but -why- move it to private?
>
> This library has been around for some time, and there are no known
> consumers.
>
> Since there are no known consumers, there is no need for us to have the
> overhead of linking a shared library for code that only OpenRC uses.
So is your plan to convert it to a static helper library, or to have
the openrc binaries link in the necessary object files directly?
next prev parent reply other threads:[~2013-09-25 20:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-14 0:16 [gentoo-dev] rfc: status of OpenRC's public API William Hubbs
2013-09-14 1:04 ` Alexandre Rostovtsev
2013-09-14 3:48 ` William Hubbs
2013-09-14 4:47 ` Alexandre Rostovtsev
2013-09-14 13:17 ` Gilles Dartiguelongue
2013-09-14 16:35 ` William Hubbs
2013-09-14 20:59 ` Pacho Ramos
2013-09-14 23:07 ` William Hubbs
2013-09-14 23:20 ` Pacho Ramos
2013-09-15 22:39 ` Gilles Dartiguelongue
2013-09-15 4:36 ` Doug Goldstein
2013-09-16 11:28 ` [gentoo-dev] " Steven J. Long
2013-09-16 22:20 ` Rich Freeman
2013-09-18 12:05 ` [gentoo-dev] " Steven J. Long
2013-09-21 19:06 ` [gentoo-dev] " William Hubbs
2013-09-21 19:21 ` Ian Stakenvicius
2013-09-24 18:15 ` William Hubbs
2013-09-24 18:22 ` Ian Stakenvicius
2013-09-25 20:04 ` William Hubbs
2013-09-25 20:27 ` Mike Gilbert [this message]
2013-09-25 21:01 ` William Hubbs
2013-09-25 21:45 ` Mike Gilbert
2013-09-25 23:08 ` [gentoo-dev] " Michał Górny
2013-09-30 12:39 ` Douglas Freed
2013-09-30 16:50 ` William Hubbs
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=CAJ0EP41RySjREWiBmDVaJA302-PKs8adRV_yQ1N76B_Zinyq6A@mail.gmail.com \
--to=floppym@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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