<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi Dafydd,<br>
<br>
<div class="moz-cite-prefix">Am 20.10.2015 um 11:58 schrieb Dafydd
Jones (techneg.it):<br>
</div>
<blockquote
cite="mid:CA+Mg1C3+z9TFCTUZQns712cJBv0+SqA3oEWFuDegFJLb2Nqq6g@mail.gmail.com"
type="cite">Holger,
<div><br>
</div>
<div>looking at your ccm package, the issue is how you
differentiate config versions.</div>
<div>You use an exists check, but the file already exists. </div>
</blockquote>
I don´t think that this causes the problem. Reason I: the second
time i executed the package, the chained package wasn´t even
processed (i verified this with the /debug parameter)<br>
Reason II: i deleted some of the files that have been copied the
first time - the second time they didn´t reappear.<br>
<blockquote
cite="mid:CA+Mg1C3+z9TFCTUZQns712cJBv0+SqA3oEWFuDegFJLb2Nqq6g@mail.gmail.com"
type="cite">
<div>I use a filesize check, because when I change a configuration
that often changes the file size, and when it doesn't I add some
extra comment. You could also compare the date of a file.</div>
</blockquote>
I guess it depends on the situation if a filesize check is
preferable to "execute=once". Having 5 big files and only one of
them changes -> use filesize check. Have 3 little txt-files and<br>
one or all changes ->execute=once will do it.<br>
<blockquote
cite="mid:CA+Mg1C3+z9TFCTUZQns712cJBv0+SqA3oEWFuDegFJLb2Nqq6g@mail.gmail.com"
type="cite">
<div><br>
</div>
<div>On upgrade, you only increment the config package revision
number, not both.</div>
</blockquote>
I will try this out.<br>
Thanks,<br>
Holger<br>
<blockquote
cite="mid:CA+Mg1C3+z9TFCTUZQns712cJBv0+SqA3oEWFuDegFJLb2Nqq6g@mail.gmail.com"
type="cite">
<div><br>
</div>
<div>HTH,</div>
<div>Dafydd</div>
<div><br>
On Tuesday, 20 October 2015, Holger Kröber <<a
moz-do-not-send="true"
href="mailto:kroeber@biom.uni-freiburg.de"><a class="moz-txt-link-abbreviated" href="mailto:kroeber@biom.uni-freiburg.de">kroeber@biom.uni-freiburg.de</a></a>>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
often, after you´ve deployed a package some changes or
modifications are required for this package.<br>
E.g. you have to (re-)configure the proxy settings for firefox
etc.<br>
I think that most of you implement change and config managment
(ccm) directly inside the package of the application itself.<br>
But what happens, if you already deployed the package and then
you have to configure some settings for this package later?<br>
The way wpkg works, you would have to modify the app package,
add some check conditions (e.g. with firefox: check file<br>
exists mozilla.cfg etc), increase the revision number
and....accept that wpkg will reinstall your complete
application/package<br>
and not just only makes the desired configuration changes.
Maybe it´s ok for you with a small package like firefox - but
there also exists big software.<br>
<br>
So i am searching for a way to avoid a reinstallation of a
already installed package while deploying new settings for
this package.<br>
My first thought was to outsource the ccm into a new package
(firefox_ccm) and then chain this package to the app package
(firefox-esr).<br>
This will work if the app package is installed for the first
time. If i later update the ccm package (because i have to
deploy new settings) and<br>
increase the revision number for both packages and then call
the app package, the chained ccm package will be ignored.<br>
I use precheck-upgrade="always" in my packages - if i remove
this line the chained package will not be ignored - but than i
will have<br>
again the problem that the complete application reinstalls. So
i guess that chained packages only work in install-mode, not
in upgrade-mode<br>
when using precheck-upgrade="always". Maybe i have to use a
different approach...<br>
<br>
How you guys manage ccm in your environment? Got some tips for
me?<br>
<br>
Thanks,<br>
Holger<br>
<br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">-------------------------------------------------------------------------
SSLrack - get your cheap cheap SSL certificates (standard, wildcard, EV)
<a class="moz-txt-link-freetext" href="http://www.sslrack.com/">http://www.sslrack.com/</a>
-------------------------------------------------------------------------
wpkg-users mailing list archives >> <a class="moz-txt-link-freetext" href="http://lists.wpkg.org/pipermail/wpkg-users/">http://lists.wpkg.org/pipermail/wpkg-users/</a>
_______________________________________________
wpkg-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:wpkg-users@lists.wpkg.org">wpkg-users@lists.wpkg.org</a>
<a class="moz-txt-link-freetext" href="https://lists.wpkg.org/mailman/listinfo/wpkg-users">https://lists.wpkg.org/mailman/listinfo/wpkg-users</a>
</pre>
</blockquote>
<br>
</body>
</html>