On Wed, Sep 25, 2013 at 7:08 PM, Michał Górny <mgo...@gentoo.org> wrote: > Dnia 2013-09-13, o godz. 19:16:06 > William Hubbs <willi...@gentoo.org> napisał(a): > >> 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 and getting rid of the >> API. > > I won't oppose since I don't use OpenRC anymore and therefore my > opinion doesn't really matter here. However, I can't help but notice > a particular trend since Roy left the project. I see that OpenRC is > slowly regressing towards baselayout-1. > > First the oldnet thingie being made the default back. While I can > understand why people wanted it so badly, this doesn't make this less > of a carousel for Gentoo users. I mean, changing defaults with every > maintainer change. > > Then, functions.sh split. While itself good, I don't get what's > the benefit of converting the bash script from baselayout-1 while > a better one was provided with OpenRC. > > Now removing the public API because you don't care. While it may have > been unused indeed, it's simply crippling the thing, not making it more > useful. > > I'd like to see some kind of plan behind all this. Because as far as I > can see, it's just new maintainers slowly dropping all the new features > they don't care about without any specific vision. No offense intended. > > If OpenRC really wants to compete with systemd, it should at least have > some design plan, and you really should start working on providing > useful features rather than reverting, crippling and rewriting for > the sake of changing things. > > Just some material to think about. > > -- > Best regards, > Michał Górny
I know I'm a bit late to this thread, but mgorny has a point. While it may not be immediately obvious, libeinfo is very useful, especially if your project aims to integrate nicely into a Gentoo system, by providing a standard set of printing functions with the formatting taken care of, resulting in output that is very familiar to users and is easy to scan with the eyes when looking for problems. One potential use-case would be reimplementing eselect in C. Not that I'm saying that this should happen, but anybody who attempts to do this would certainly appreciate having this bit taken care of for them. I would be more than willing to assist with maintenance of the library, even if split out into its own package, since it's small and rather simplistic, so there's unlikely to be any issues. I see no reason why we should remove something that isn't broken and doesn't cause us any maintenance burden. If somebody does open a bug against OpenRC because of an issue they're encountering while trying to use libeinfo, I give full license to assign the bug to me, and I'll happily investigate the issue. -Doug
