<html><body>
<br /><blockquote>Fr Okt 03 2008 07:06:56 CEST von Michael Meskes an pkg-citadel-devel@lists.alioth.debian.org <br />Betreff: [Pkg-citadel-devel] tarballs<br /><br />Will we get new 7.38 tarballs on citadel.org, or do we have to patch to fix<br />that setup bug?<br /><br />I also found the reason for the setup prolem with the fix included. Our postinst has this:<br /><br />...<br /> export CITADEL=''<br />...<br /> /usr/lib/citadel-server/setup -q<br />...<br /><br />Removing the export (why is it there anyway?) makes the package configure.<br /><br />Looking at the packages at citadel.org I found that those packages have:<br /><br />...<br /> export CITADEL='/var/run/citadel'<br />...<br /><br />Is there a reason why those packages still have their own packaging and do not use the Debian packaging?<br /><a href="http://lists.alioth.debian.org/mailman/listinfo/pkg-citadel-devel" target="webcit01"></a><br /><br /></blockquote><p>Upsie; sorry for causing inconvenience.</p><p>I didn't take the time to migrate my infrastructure to the pkg-citadel debs; I also thought of them rather following citadel.org release cycles directly than adding patches.</p><p>Plus my upstream citadel development work uses some of the debug switches removed from the pkg-citadel debs. Thus I also tend to alter them to follow SVN Head for that reason, I don't know if thats a good tactic for pkg-citadel. </p><p>Though i've tried to keep them as similar as possible, so that there shouldn't be problems to Users switching back and forth.</p><p> </p><p>Wilfried Goesgens </p>
</body></html>