Patching strategy

Could be a dumb question but here it goes.  In the past I've downloaded 
and used many of the NDK builds for PHP, MySQL, and Apache only to find 
out that the Netware support packs overwrite them with the older version 
in the SP.  What is everyone doing with their custom built boxes when a 
Netware support pack comes out?

Thanks,

Hi Sean,
sean <user@example.net> wrote in news:UbG8h.30$jS4.12@prv-
forum2.provo.novell.com:

> Could be a dumb question but here it goes.  In the past I've downloaded 
> and used many of the NDK builds for PHP, MySQL, and Apache only to find 
> out that the Netware support packs overwrite them with the older version 
> in the SP.  What is everyone doing with their custom built boxes when a 
> Netware support pack comes out?
I do suffix the folder names with '.nov' bevor I do an own install, and later 
when I want to install a service pack then I rename back, f.e.:
sys:/php5 => sys:/php5.nov
sys:/mysql => sys:/mysql.nov

bevore installing service pack I do:
sys:/php5     => sys:/php5.my
sys:/php5.nov => sys:/php5

sys:/apache2 is a special case because there are a couple of files inside the 
directory structure which prevent from the above scheme - so there I normally 
avoid updating; instead I use a new instance of my Apache 2.2 which has 
sys:/apache22 as basedir, and therefore never gets touched by the SP.
Another option if you really want to update the sys:/apache2 is that you 
simply zip the folder bevore installing the SP, and later extract again to 
restore your own version.

HTH, Guen.

Thanks Guenter, good suggestion.  What do you do to keep LibC from being 
backreved?  Just reinstall the NDK version again?

Sean

Guenter wrote:
> Hi Sean,
> sean <user@example.net> wrote in news:UbG8h.30$jS4.12@prv-
> forum2.provo.novell.com:
> 
>> Could be a dumb question but here it goes.  In the past I've downloaded

>> and used many of the NDK builds for PHP, MySQL, and Apache only to find

>> out that the Netware support packs overwrite them with the older
version 
>> in the SP.  What is everyone doing with their custom built boxes when a

>> Netware support pack comes out?
> I do suffix the folder names with '.nov' bevor I do an own install, and
later 
> when I want to install a service pack then I rename back, f.e.:
> sys:/php5 => sys:/php5.nov
> sys:/mysql => sys:/mysql.nov
> 
> bevore installing service pack I do:
> sys:/php5     => sys:/php5.my
> sys:/php5.nov => sys:/php5
> 
> sys:/apache2 is a special case because there are a couple of files inside
the 
> directory structure which prevent from the above scheme - so there I
normally 
> avoid updating; instead I use a new instance of my Apache 2.2 which has 
> sys:/apache22 as basedir, and therefore never gets touched by the SP.
> Another option if you really want to update the sys:/apache2 is that you 
> simply zip the folder bevore installing the SP, and later extract again to

> restore your own version.
> 
> HTH, Guen.

Hi Sean,
sean <user@example.net> wrote in
news:3iI8h.171$jS4.30@prv-forum2.provo.novell.com: 

> Thanks Guenter, good suggestion.  What do you do to keep LibC from being
> backreved?  Just reinstall the NDK version again?
hmm, that should normally never happen since a new SP _should_ contain all 
previously published NWLIBx fixes - so after SP install the NWLIBx becomes 
obsolete.

greetz, Guenter.