On 05 Apr 2011, at 12:28 AM, Alessandro Dentella wrote: > > > I built it myself from git repo, that probably means I really build a 1.1.x > even if the debian/control still refers (and builds) 1.0.2
Cool, i thought so too. > > good, that leads to 2 more questions. Do you already have a idea on the > release period for the 2.x branch? and more important will that introduce > some problems in upgrade (e.g. model structure). If I start now with 1.0.2 > will it be hard to upgrade? The ability to upgrade is at the heart of all design and development decisions, if you start using 1.0.2 now be assured that there will always be an easy upgrade path. Moving to 1.1.x will be pretty easy. But being Python/Django savvy i would say dive into 1.1.x directly and help fix the bugs that pop up. 2.x is still a long way down as it uses pylons + sqlalchemy + mako for this there will be a paster command that automatically does the conversion. > > I didn't know about it. It's an interesting feature of mailscanner, it's a > pity that squeeze only has mailscanner 4.79.11... This is being worked on, on two fronts Achim is trying to get the official debian package updated and i am working on always providing the latest mailscanner deb package in the baruwa ppa http://lists.mailscanner.info/pipermail/mailscanner/2011-March/097669.html http://lists.mailscanner.info/pipermail/mailscanner/2011-March/097689.html . > > If I understand correctly that means putting mailscanner conf + baruwa > (django std + baruwa specific) in the same db... at that point it shouldn't > be difficult to read mailscanner.conf from within settings.py! Yes and no, the mailscanner and baruwa will use the same DB the django+baruwa configurations will remain in settings.py but all the perl modules will use the standard sql settings in the mailscanner.conf file. Anyway when i implement SQLConfig fully we will do away with the whitelist/ blacklisting custom functions module may be even the usersettings. > > As a last note: settings.py in my opinion should live under /etc/* at least > in the debian package That is a given, settings.py will move into /etc/baruwa, and for the debian package i will install a baruwa.conf in /etc/mailscanner/conf.d which means you may not have to even edit anything. -- Baruwa - www.baruwa.org _______________________________________________ Baruwa mailing list [email protected] http://lists.baruwa.org/mailman/listinfo/baruwa
