[gentoo-dev] rfc: openrc c api (librc) usage

[gentoo-dev] rfc: openrc c api (librc) usage

[William Hubbs]

[-- Attachment #1: Type: text/plain, Size: 875 bytes --]

All,

I want to start a discussion about the usage of OpenRC's C api as
defined in rc.h.

I have no idea which projectss out there are using it, or which
functions they are using.

There are two functions I can deprecate immediately and prepare to drop
in 1.0 -- these are rc_getline() because getline() is now a posix
function, and rc_sys() because the OpenRC internal code no longer uses
it and because it is broken (it doesn't distinguish between containers
and virtual machines).

What I want to know is,

- Which projects include rc.h?

- What are you using in rc.h?

From my perspective it looks like a number of the functions in librc are
probably functions that should be internal to OpenRC instead of being
shared in an API; however, I don't want to knowingly break anything by
moving functions that someone is using.

Thanks,

William


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: [gentoo-dev] rfc: openrc c api (librc) usage

[Mike Frysinger]

[-- Attachment #1: Type: text/plain, Size: 528 bytes --]

On 10 Dec 2015 10:32, William Hubbs wrote:
> I want to start a discussion about the usage of OpenRC's C api as
> defined in rc.h.

very few projects ever picked up the API/libraries.  probably for the best.

> I have no idea which projectss out there are using it, or which
> functions they are using.

look at the RDEPEND in ebuilds.  if a package uses the libs, it should be
listed there.  if you don't find any of those (few) packages actually using
the API, then just make the change and wait for someone to complain.
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[gentoo-dev] Re: rfc: openrc c api (librc) usage

[Duncan]

Mike Frysinger posted on Tue, 15 Dec 2015 00:00:51 -0500 as excerpted:

> On 10 Dec 2015 10:32, William Hubbs wrote:
>> I want to start a discussion about the usage of OpenRC's C api as
>> defined in rc.h.
> 
> very few projects ever picked up the API/libraries.  probably for the
> best.
> 
>> I have no idea which projectss out there are using it, or which
>> functions they are using.
> 
> look at the RDEPEND in ebuilds.  if a package uses the libs, it should
> be listed there.

Even with openrc still in @system?  Doesn't look like that bug has been 
fixed yet.[1]

> if you don't find any of those (few) packages actually
> using the API, then just make the change and wait for someone to
> complain.

With openrc still in @system, that's probably the way it'll need to be 
handled, tho ideally everything that needs it will be RDEPENDing on it by 
now in preparation for removing openrc from @system, so nothing will 
break.

---
[1] I've had my entire @system negated in /etc/portage/profiles/packages 
since long before I switched to systemd, and after symlinking
/etc/init.d/functions.sh -> /lib/gentoo/functions.sh, I unmerged openrc.  
So to see if it was in the normal @system I had to manually check if 
openrc was still starred in a packages file any of the broadly sourced 
profiles and it is, in base, with the only negations in the prefix and 
freebsd profiles.

Obviously nothing I run breaks without any of the other files openrc 
provided, but that doesn't mean nothing else in the tree does.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

Re: [gentoo-dev] Re: rfc: openrc c api (librc) usage

[Michael Orlitzky]

On 12/16/2015 01:44 AM, Duncan wrote:
>>
>> look at the RDEPEND in ebuilds.  if a package uses the libs, it should
>> be listed there.
> 
> Even with openrc still in @system?  Doesn't look like that bug has been 
> fixed yet.[1]
> 

No one agrees on which @system packages can be omitted from (R)DEPEND.
The devmanual says that they can all be omitted:

https://devmanual.gentoo.org/general-concepts/dependencies/index.html#implicit-system-dependency

But a lot of people will tell you that if you link to some library (say,
libz) from a @system package, you should still include it in RDEPEND.
That makes sense, since we now have features that can make use of that
information. I think this is what vapier meant.

And then opinion (2.a) is that the last rule is correct, except for
certain things (like libc) that "everyone" links to.

Re: [gentoo-dev] Re: rfc: openrc c api (librc) usage

[Mike Frysinger]

[-- Attachment #1: Type: text/plain, Size: 719 bytes --]

On 16 Dec 2015 06:44, Duncan wrote:
> Mike Frysinger posted on Tue, 15 Dec 2015 00:00:51 -0500 as excerpted:
> > On 10 Dec 2015 10:32, William Hubbs wrote:
> >> I want to start a discussion about the usage of OpenRC's C api as
> >> defined in rc.h.
> > 
> > very few projects ever picked up the API/libraries.  probably for the
> > best.
> > 
> >> I have no idea which projectss out there are using it, or which
> >> functions they are using.
> > 
> > look at the RDEPEND in ebuilds.  if a package uses the libs, it should
> > be listed there.
> 
> Even with openrc still in @system?  Doesn't look like that bug has been 
> fixed yet.[1]

if you link against openrc, you need to RDEPEND on it
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]