Trevor,
for a very long time it was not the case, that an old feature has required
an updated version of a module (some are recommended). I think the last
required module updates where needed for SSL support/DKIM, all others are
recommended.
Some new features may require an additional module, but this should not
affect any other features. If a new version will require (I hope I can
prevent this) any module update, the autoupdate feature will stop working,
until a manual upgrade was made or the version.txt file was deleted.
I know, I've changed the Regex::Optimizer requirement - but if someone is
not using the new 1.07, this will not have any issue to the functions of
assp, except that it is running a bit slower and it needs some more
memory.
Long time ago, I was thinking about a module autoupdate, but this will not
work. On nix the right kernel sources and gcc must be available, on
windows some vcredist versions must match, some software must be available
with right version (OpenSSL ...) or source - some other software could be
affected - 32 and 64 bit - ...... - this is a never ending list - and
will become a never ending story if started.
As I remember, you use Perl 5.8.8 - right? If so, keep in mind, that I
keep an eye on the code, that no 5.10++ unique statement are used - but
this could be happen and I never do any tests on 5.8.8!
And the days of the 5.8.8 support are counted. An new version 2.0.3 or
2.1.0 will possibly require 5.10.
Thomas
Von: Trevor Jacques <[email protected]>
An: ASSP development mailing list <[email protected]>
Datum: 16.09.2010 16:39
Betreff: Re: [Assp-test] fixes and changes in 2.0.2_1.2.10
I was away for a week, and was told by users that SMTP stopped for them
some time before midnight on Tuesday evening. I tried going back to .09
and .08, but it did not work, so I used a Time Machine backup of settings
from Tuesday ten days ago (I LOVE Time Machine for this). The server seems
to be processing SMTP connexions again. Phew....
FWIW, I noticed in the Connections window that SMTP communications
appeared to have started, but had somehow stalled for some reason.
I went back to the initial notice about version .10 and noticed a new perl
module requirement. MAYBE there was a versioning conflict, so I am in the
process of upgrading the modules as I type this. If I find anything, I'll
report it.
I've had similar problems before, when the automated update starts with a
new, but problematical, version. I've no way of knowing until one of my
users bleats, or I notice my mailing has problem. As a result, I've
decided to turn off automatic updates, because this 'phantom' failure mode
has happened several times before (as a result of various causes in the
betas), and I can't afford to have this happen again to an otherwise
stable assp. Yes, I now realise that it's best to stop automatic updates
when I'm away, but I also realise that there may be a better way to handle
the automatic updates. If the new version requires a new version of a perl
module and that version is not available (and the respective setting of
assp is set to use the function that calls the perl module), then, Thomas
had said in earlier instances of this problem at least a year ago, assp
should simply disable those functions. Admittedly, this means both
comparing the perl versions and whether the settings of assp use the perl
modules. It's not really a problem for manual upgrades, since assp can
reasonably require that we RTFM. This is not easily done for automated
updates of assp. I've no doubt that the conundrum is as frustrating to
Thomas as it is to users. :-/
HTH,
T.
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test
DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally
privileged and protected in law and are intended solely for the use of the
individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no
known virus in this email!
*******************************************************
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test