Ludovic, could you please comment on the status here? Can we build SOGo and all it's dependencies from upstream gnustep, SOPE, etc.. or are there special "SOGo"-versions of these we'll need? And what is the relationship between SOPE 2.0.7 from http://www.sogo.nu/files/downloads/SOGo/Sources/ and SOPE from http://sope.opengroupware.org/ ? Which one should Fedora provide? Ref: https://lists.fedoraproject.org/pipermail/devel/2013-October/190217.html for start of thread. -jf On Wed, Oct 16, 2013 at 06:22:41PM +0200, Sandro Mani wrote: > On 16.10.2013 18:13, Jan-Frode Myklebust wrote: > >I'm using sogo on RHEL6 at work, and would gladly help maintaining it > >for Fedora. But, I've been expecting this would be a difficult job > >because I thought SOGo/inverse maintained their own patched gnustep, > >sope or something like that. Is that not the case? > The only change I needed for GNUStep was applied to Fedora [1]. Now, > everything works fine from what I see (though my current setup is > not terribly complex). Obviously, more testing is more than welcome > :) > >For RHEL6 we're using sope 4.9 from SOGo's own repository, not the > >2.0.7 version you have packaged.. And what's the real upstream for SOPE? > >sogo.nu or http://sope.opengroupware.org/en/source/index.html ? > That also confused me. Ultimately I ended up looking at the release > dates (SOPE-2.0.7 from [2] was released 23 Jul 2013, sope-4.7.1 from > opengroupware was released 01 Jul 2007). Plus, I also had a look at > what debian did, and they packaged 2.0.7 from sogo. > > > Sandro > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1005328 > [2] http://www.sogo.nu/files/downloads/SOGo/Sources/ > -- > devel mailing list > devel@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/devel > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
