Hi all,

I finally feel confident enough to do a new public release.
Unfortunately only tarballs this time around. Doing distribution
specific releases simply takes to much time away from my coding. We
can't have that...

But - generating a distribution specific installation file should be
easy. Just do:

$ ./autogen.sh && make release

and you should end up with rpms, an ebuild or debs depending on your
platform.

This release fixes all known problems with e-b including those start-up
problems and runtime CORBA exceptions that has been mentioned on the
brutus list.

Getting debug output is now much simpler than before. No need to start
Evolution or evolution-data-server from a terminal. The only thing you
need to do is to create "~/.brutus-do-debug". 

The presence of this file (which could be a link or even a directory)
will make the log daemon append debug output from all e-b components to
"~/.brutus-logd/brutus.log". Delete this file and the debug output will
no longer go to the log file or anywhere else for that matter. 

>From the using_evolution-brutus document:

############### Excerpt start ###############
Reporting problems
==================

You can always help by reporting problems to <[EMAIL PROTECTED]> or preferably 
to
the evolution-brutus trac: 

    <http://trac.brutus.net/evolution-brutus/>

or by subscribing to the brutus mailing list and posting your problem to the 
list:

   <http://www.omesc.com/mailman/listinfo/brutus/>

evolution-brutus, if build with debugging support, will generate a nice log 
that 
you are encouraged to attach to your problem report. To tell evolution-brutus 
to 
generate the log just create a file named ".brutus-do-debug" in your home 
directory. It doesn't need to be a regular file. It could be a directory or a 
link.

All log output will be appended to "~/.brutus-logd/brutus.log" by the Brutus 
Log 
daemon. Please append this file to all bug reports and describe how to 
reproduce 
the problem if possible.

You can tell the log daemon to restart itself and start all over with an empty 
log file. Just send SIGUSR2 to the log daemon:

      $ kill -s USR2 $(cat ~/.brutus-logd/brutus-logd.pid)
################ Excerpt end ################

The only downside to this release is that you need ORBit2 from svn. Any
younger versions have know bugs that will make e-b crash or (if you are
lucky) merely misbehave, YMMV.

To use this release you will need:

Brutus Server 0.9.36:
http://www.omesc.com/sites/default/files/downloads/brutus-install.exe

brutus-keyring:
http://www.omesc.com/sites/default/files/downloads/dist/brutus-keyring/SOURCES/brutus-keyring-0.9.11.tar.gz

evolution-brutus:
http://www.omesc.com/sites/default/files/downloads/dist/evolution-brutus/SOURCES/evolution-brutus-1.1.29.23.tar.gz

ORBit2 from svn:
$ svn co svn://svn.gnome.org/svn/ORBit2/trunk ORBit2


Best regards,
  jules




_______________________________________________
Evolution-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/evolution-list

Reply via email to