On Wed, Sep 25, 2013 at 5:01 PM, William Hubbs wrote:
> On Wed, Sep 25, 2013 at 04:27:42PM -0400, Mike Gilbert wrote:
>> On Wed, Sep 25, 2013 at 4:04 PM, William Hubbs wrote:
>> > On Tue, Sep 24, 2013 at 02:22:02PM -0400, Ian Stakenvicius wrote:
>> >> -BEGIN PGP SIGNED MESSAGE-
>> >> Hash
On Wed, Sep 25, 2013 at 04:27:42PM -0400, Mike Gilbert wrote:
> On Wed, Sep 25, 2013 at 4:04 PM, William Hubbs 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 Wed, Sep 25, 2013 at 4:04 PM, William Hubbs 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:
>>
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 thes
-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
On Sat, Sep 21, 2013 at 03:21:07PM -0400, Ian Stakenvicius wrote:
> -BEGIN PGP SIGNED MESSAGE-
> IIRC we still don't have an openrc-replacement script in the tree for
> the /etc/init.d/function.sh symlink to target. Since libeinfo is
> already public, why not instead of making it private w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 21/09/13 03:06 PM, William Hubbs wrote:
> All,
>
> this is a followup to the original message that started this
> thread.
>
> A case has been made for librc, but not libeinfo. There could be
> reasons to allow the librc functionality to stay a
All,
this is a followup to the original message that started this thread.
A case has been made for librc, but not libeinfo. There could be reasons
to allow the librc functionality to stay around, but I'm not convinced
wrt libeinfo, especially since there are no consumers.
Does anyone see a reaso
On Mon, Sep 16, 2013 at 7:28 AM, Steven J. Long
wrote:
> It's only an issue at system-level when your code is dependent on what the
> higher layer is going to do with your output, or requires a specific higher
> layer to run at all(!).
I think the real issue is the lack of any kind of standardiza
On Fri, Sep 13, 2013, William Hubbs wrote:
> OpenRC currently has a public api, consisting of librc and libeinfo
> (rc.h and einfo.h are the headers); however, I do not know of any
> released software that uses these, so, if there is nothing, I am
> considering making this code private to OpenRC an
10 matches
Mail list logo