Upgrading Minor versions

Julian Field MailScanner at ecs.soton.ac.uk
Fri Aug 3 11:42:43 IST 2007

Res wrote:
> On Fri, 3 Aug 2007, Glenn Steen wrote:
>> That scheme was dreamed up in the linux kernel dev... and (perhaps...
>> It was not always so:-) suits them very well. And it has spilled over
>> on a lot of projects. But it is hardly the one true unified version
> spilled over to just about 90% of the software around :)
>> And it's not sure to cure anything like this, where _packaging
> it would, as it would install to /opt as 4.63.b2 etc and not over 
> write the existing 4.63 directory.
>> will just have to think of some more or less clever way of handling
>> it.
> and until such time, its probably going to be recommended those using 
> tarball don't bother with such upgrades.
I don't need to completely rewrite my version numbering scheme or 
anything crazy like that. All I need is to add 4 characters to 

Please try the attached patch. You will discover it adds the build 
number in the directory it creates for the new version of MailScanner 
you're installing.


Julian Field MEng CITP
Buy the MailScanner book at www.MailScanner.info/store

Need help customising MailScanner?
Contact me!
Need help fixing or optimising your systems?
Contact me!
Need help getting you started solving new requirements from your boss?
Contact me!

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654

This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
For all your IT requirements visit www.transtec.co.uk

-------------- next part --------------
A non-text attachment was scrubbed...
Name: install.tar-fns.sh.patch.gz
Type: application/x-gzip
Size: 330 bytes
Desc: not available
Url : http://lists.mailscanner.info/pipermail/mailscanner/attachments/20070803/24f4a9f6/install.tar-fns.sh.patch.gz

More information about the MailScanner mailing list