Re: [Log4cpp-devel] Joining/merging the different log4c** implementations?

[Konstantin L. <to....@gm...>]

On 02/02/2012 09:29 PM, Palic, Darko wrote:
> Hello list,
>
> I love log4j and log4net. And I would like to love log4c**. BUT, there
> are at least 3 implementations I found for log4c**. Right now I am using
> log4cxx from apache.org. I would like to be able to use the same logging
> configurations for the my different application types. Isn't is perfect
> to configure the logging in every major language in the same way? Isn't
> it a really nice option to change the log level by changing a simple
> config file? And isn't it nice to do it in the same way in java, c# or
> c/c++?

Nothing preventing you from doing that. Just write for each package same 
configuration code and have it. log4cpp van be configured in log4j way, 
I think...

>
> But what I am trying to address with this mail?
> log4cxx seems to be dead (no responses of developers, patches of user
> aren't integrated for a long time, no commits since a very long time). I
> decided to check also some alternative. I was looking into the log4cpp
> repository and this also seems to be dead.
> So I was wondering if there are more projects implementing log4c**. I've
> found log4cplus, this seems to be a "sort of active".

These project seems to be dead because they riches a level of maturity 
where 90% of user get what they need.

>
> Now I am wondering why it is necessary to maintain 3 projects which have
> the same idea. Wouldn't it be more efficient for all projects, if the
> available contributors and developers would maintain one and the same
> project? So I am wondering if it wouldn't be possible to merge the
> projects into one sourcetree? Lets say a new log4cpp which has all
> features and enhancements of all log4c** projects.

Because that is what open source is :) Different people from different 
reasons started these projects. Yes, they share same idea, but differs 
in implementation. I think it common to have more then one project doing 
the same thing in open source land.
I don't think merging is good idea because all these project already 
stops they evolution, have static user base. I don't think I'll move to 
super-log4cpp just because it here.
When I choose to stick log4cpp I look at functionality, which is the 
same for all logging projects, AND simplicity of build. The major 
problem is the BUILD. When you do only *nix development you just pick 
some lib and go. BUT. When you do *nix/Windows development you are in 
trouble. There is NO clearly defined way to packaging and distributing 
libs on Windows. So you must choose some lib that have less dependencies 
and can be build in a simple way.
Unified packaging and distributing system for C/C++ is a major problem 
for C/C++ developers and until it will be resolved there is no way to go...