José Parrella
2006-11-26 03:13:55 UTC
Greetings,
My name is Jose Parrella, and I'm packaging ASSP for the Debian Free
Software Distribution. I've been using ASSP in commercial clients in
Venezuela since January with a high success rate, and lots of interest
in having an ASSP package. One of the big show stoppers for a Debian
package of ASSP is the way it handles the paths for files. I'm aware of
a previous thread about this in [1], which I would like to address again.
Is it feasible to split $base in several variables? I have started to do
some work towards it, but I'm afraid that the work could collide, or
even worst, that my work might break the situation for Windows users (I
really don't expect that, though)
Several issues need to be revised in order to provide some structure to
the way ASSP handles paths. One easy patch is to substitute all images/
links with, say, /usr/share/assp/images. You can do this easily using a
variable expansion and search and replace.
Some of the paths can be specified in the configuration file, for
example the maillog.txt path, and the paths for redre.txt and
nodelay.txt, as well as the paths for the spamdb, and the errors/
folder. This ease up a little bit the issue, but forces the maintainer
to provide an assp.cfg file, since newer versions of ASSP don't provide
a separate assp.cfg.
Another issue arises regarding the mkdir calls, which needs to be
wrapped inside a "if it doesn't exists", thus avoiding failures, and
also needs some sanity controls before proceeding, in order to avoid the
creation of directories in random directories. rebuildspamdb.pl also
needs to get this changes.
assp.pl also needs to be transformed from DOS to Unix format in order to
be invoked by the start-stop-daemon in Debian through an init.d script.
I'll be working on all of these issues trying to be the less intrusive
possible, and I'll provide patches when all the changes work in a sane
way. But I would like feedback on this issue, specially if someone's
already working on that, or if I'm missing an obvious solution, or if
this involves a design decision.
Thank you all very much for making ASSP a great software, and have a
nice day.
[1]
http://sourceforge.net/mailarchive/forum.php?thread_id=7252241&forum_id=39228
My name is Jose Parrella, and I'm packaging ASSP for the Debian Free
Software Distribution. I've been using ASSP in commercial clients in
Venezuela since January with a high success rate, and lots of interest
in having an ASSP package. One of the big show stoppers for a Debian
package of ASSP is the way it handles the paths for files. I'm aware of
a previous thread about this in [1], which I would like to address again.
Is it feasible to split $base in several variables? I have started to do
some work towards it, but I'm afraid that the work could collide, or
even worst, that my work might break the situation for Windows users (I
really don't expect that, though)
Several issues need to be revised in order to provide some structure to
the way ASSP handles paths. One easy patch is to substitute all images/
links with, say, /usr/share/assp/images. You can do this easily using a
variable expansion and search and replace.
Some of the paths can be specified in the configuration file, for
example the maillog.txt path, and the paths for redre.txt and
nodelay.txt, as well as the paths for the spamdb, and the errors/
folder. This ease up a little bit the issue, but forces the maintainer
to provide an assp.cfg file, since newer versions of ASSP don't provide
a separate assp.cfg.
Another issue arises regarding the mkdir calls, which needs to be
wrapped inside a "if it doesn't exists", thus avoiding failures, and
also needs some sanity controls before proceeding, in order to avoid the
creation of directories in random directories. rebuildspamdb.pl also
needs to get this changes.
assp.pl also needs to be transformed from DOS to Unix format in order to
be invoked by the start-stop-daemon in Debian through an init.d script.
I'll be working on all of these issues trying to be the less intrusive
possible, and I'll provide patches when all the changes work in a sane
way. But I would like feedback on this issue, specially if someone's
already working on that, or if I'm missing an obvious solution, or if
this involves a design decision.
Thank you all very much for making ASSP a great software, and have a
nice day.
[1]
http://sourceforge.net/mailarchive/forum.php?thread_id=7252241&forum_id=39228
--
José M. Parrella -> Debian Sid, k2.6.17.13
Escuela de Ingenieria Electrica
Universidad Central de Venezuela -> ucvlug.info
José M. Parrella -> Debian Sid, k2.6.17.13
Escuela de Ingenieria Electrica
Universidad Central de Venezuela -> ucvlug.info