<div class="gmail_quote">On 8 June 2010 18:25, Paul W. Frields <span dir="ltr"><<a href="mailto:stickster@gmail.com">stickster@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">We can check using 'rpm -V zikula'. I found that other than our</div>
/etc/zikula/config.php file (expected differences), there's a change<br>
that's been made directly on /usr/share/zikula/includes/ZLanguage.php.<br>
<br>
I want to remind our Zikula friends that making these changes directly<br>
on the system is *discouraged* since we use packaged software from<br>
EPEL to deploy Zikula. This may be a patch that was tested and simply<br>
not removed. If that kind of change is not documented, however, it<br>
raises the risk of regressions when we upgrade.<br></blockquote><div><br></div><div>Yes, this change is in 1.2.3. I worked on the bug you were experiencing (symbolic links to zikula install meant ZLanguage was unable to locate the locale files). This was fix upstream and patched into your local install. We release Zikula 1.2.3 around 5-6 weeks ago with this change.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">We need to realize that some of the things we're dealing with right</div>
now -- maintaining the platform and modules, testing functionality --<br>
are going to be the same needs regardless of our choice of platform.</blockquote><div><br></div><div>I'd also like to point out that for reasons I am not quite sure of, FI has taken months and months when it should have taken just a few days - people regularly deploy vastly complex Zikula sites in a matter of days. Future upgrades will be quite painless I can assure you, but I would really like to do assist in the packaging process. I think it would be far better (broken record again), if we put all the RPM building on our CI server, then a large portion of the packaging work would be done. All that would remain is testing and tweaking. Since tweaks would be made to the build XML it means future packaging would be even more painless.</div>
<div><br></div><div>Regards,</div><div> </div><div>Drak</div><div> </div></div>