[Fusionforge-general] merge fusionforge novaforge

christian.bayle at orange-ftgroup.com christian.bayle at orange-ftgroup.com
Wed Feb 18 17:55:02 CET 2009


Hi,
> 
> I don't understand the aim of this merge.
> Merge new functionnalities for LDAP, code amelioration or new 
> plugins, that's great. But merge a whole config system 
> specific to novaforge, what will be the gain for novaforge 
> and for fusionforge ?

In fact all the ldap stuffs are not to merge as they are recent changes
The only thing to merge is the .spec renaming and add the missing dir
from novaforge 
tree in trunk

The only think are config specific, and having the 2 config in the same
place 
should make easy to merge

The aim is mainly not to have to continuously update novaforge branch.

The idea is to do as soon as possible a build server that both build all
forge stuffs
so we can see when a change is breaking something

I'm almost sure the .spec renaming is breaking novaforge build, but this
may be very simple change 
to do in novaforge build, that the build system would help for.

I don't actually know what apacheconfig stuff is the best, but i'd like
to have only one for sure.
the same for cron.

I think that cron could probably easily unified, but I have to know if
my change for debian don't break rpm
or novaforge build.

The other big thing of the merge is to make available novaforge extra
plugin for rpm and deb.


Christian




More information about the Fusionforge-general mailing list