On Wed, Jan 29, 2014 at 12:24 AM, Michael Biebl <[email protected]> wrote:

> 2014-01-28 Rainer Gerhards <[email protected]>:
> > Hi all, and especially to the package builders on this list,
> >
> > as we all know, I screwed up when I did the initial stdlog component for
> > liblogging. I am now working on fixing this mess. First of all, the
> > components are now clearly described:
> >
> > https://github.com/rsyslog/liblogging/blob/master/README.md
> >
> > One important question is left: how would you suggest to name the
> packages?
> > For more than 10 years, the rfc3195 component came under the name of
> > "liblogging", so I would assume it's a bad idea to rename this one. Does
> > this mean we end up with
> >
> > * liblogging (rfc3195)
> > * liblogging-stdlog
> > * liblogging-journalemu
> >
> > If so, I should probably also change the names used in PKGCONFIG,
> configure
> > scripts etc. That probably means I need to do yet another rsyslog 7.4
> > release but if it takes that to clean up the mess, it's probably worth
> it.
>
>
> Is there a good reason to split them up?
>
>
>
*I* think so. The rfc3195 part, while in use by a handful of apps, is
really something that 99.98% of the folks never need, and it is a
relatively large body of code. The journalemu part you'll never need on
systems with systemd journal, and I assume that'll be the majority in
future. The stdlog component will always remain a very small component
(never say never, I know...) and so I think it would be least intrusive to
split these components into separate packages.

Rainer
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of 
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE 
THAT.

Reply via email to