Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon3.gif   move mxml code into elog's src directory, posted by Jeff Stoner on Fri Feb 15 03:16:45 2008 
    icon2.gif   Re: move mxml code into elog's src directory, posted by Stefan Ritt on Fri Feb 15 06:59:52 2008 
Message ID: 65741     Entry time: Fri Feb 15 06:59:52 2008     In reply to: 65740
Icon: Reply  Author: Stefan Ritt  Author Email: stefan.ritt@psi.ch 
Category: Request  OS: Linux  ELOG Version: 2.7.2 
Subject: Re: move mxml code into elog's src directory 

Jeff Stoner wrote:

The mxml source code should be moved into the elog-*/src directory. This requires changing the Makefile to:

MXMLDIR = src/mxml

Reason for change: if you want to build several versions of elog and you unpack the distributions in the same top-level directory, the most recently unpackaged version will overwrite the mxml directory contents, possibly introducing bugs.

From your point of view that request is reasonable, but the reason of having mxml in a separate top level directory is that I use it in many different projects. If I would keep a copy of mxml in each project, I would have to update all of them manually if there is a bug. On the other hand the code of mxml changes very seldom. If you look at the history, it got ~5 changes last year, while elog itself had hundreds. And since I do not change the API, a bugfix in mxml should be to the benefit of all elog versions. It is like with other projects which depend on a number of packages. Like if you install Apache for example, you need a certain version of OpenSLL, a certain version of libcrypt, and so on.  So think of mxml like another package you have to combine with elog.

ELOG V3.1.5-3fb85fa6