Hi Andrew, On Mon, Apr 04, 2011 at 11:40:39PM +0200, Andrew Colin Kissa wrote: > > Now some questions/notes: > > > > 0. the debian package seems to miss the python-celery dependancy that is > > required by settings.py. "pip install" followed by "dpkg-reconfigure > > baruwa" did the trick, no package is available so that configuration > > cannot work right away. > > python-celery is only required by the 1.1.x branch which has not been > released yet that is why the debian buildkit has not yet been updated. > 1.0.x should not require python-celery which deb did you use i hope > the 1.1.x tree did not pollinate the 1.0.x tree.
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 > > 1. Is there any technical reason why mysql is the default choice? I'd > > really would prefere PostgreSQL and django should work with both. As > > far as the CustomFunctions I think it would be easy to create a pg > > version, I can provide it if needed. > > Thats correct, it is possible to use pgsql, this is already implemented for > the 2.x branch. It should be as easy as using the correct DBI interface, > if we start using the configuration options from Mailscanners SQLConfig > it makes it much more portable. 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? > > 2. I don't personally like to set host/user/pass in the CustomFunctions. I > > consider them as code provided by Baruwa and they should be upgradable > > without problems. They live in /etc/MailScanner, they are indeed a > > configuration for MailScanner, but they are code for baruwa... > > In addition, the same configuration is repeated 3 times in 3 files, > > that is not very DRY. > > Correct, my proposal going forward is to use the DBI settings in > Mailscanner.conf > (the SQLConfig ones) 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... > > I propose to set configuration in another file and read that file from > > these 3 files. Ideally that should be settings.py... > > I the MW configuration I used to have a db.ini file and both > > settings.py and *.pm read they're conf from that file. > > I can provide the patch if you like the idea. > > This is what i had in mind > http://lists.baruwa.org/pipermail/baruwa/2011-February/000465.html > but that would still mean some duplication but just in two places settings.py > and mailscanner.conf but am open to discussion on the merits of your > suggestion. 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! As a last note: settings.py in my opinion should live under /etc/* at least in the debian package. 'night sandro *:-) -- Sandro Dentella *:-) http://www.reteisi.org Soluzioni libere per le scuole http://sqlkit.argolinux.org SQLkit home page - PyGTK/python/sqlalchemy _______________________________________________ Baruwa mailing list [email protected] http://lists.baruwa.org/mailman/listinfo/baruwa
