wpkg.xml - how to delete or rebuild by wpkg

[Johannes.Brix]

I have modified some definitions for packages, especially the "remove"
part.
Is it possible to force a refresh of the local wpkg.xml file without
deleting it?
If not, is there a simple way to delete it ?

If this file is not updated, it will work with the settings for update and
remove
which is written there, and not with the modifications I have done on the
server.

---------------------------------------------------------------------------
Johannes Brix, CISSP                     Phone:    ++49 (0)2 20 33 05 15 32
Senior Support Engineer                  Mobile:   ++49 (0)  17 35 88 76 48
Evidian Customer Care Köln               Web:           support.evidian.com
                                                            www.evidian.com
---------------------------------------------------------------------------
BULL - Architect of an Open World                              www.bull.com
---------------------------------------------------------------------------
CISSP - Certified Information System Security Professional     www.isc2.org
---------------------------------------------------------------------------



-------------------------------------------------------------------------
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
_______________________________________________
wpkg-users mailing list
wpkg-users@...
http://lists.wpkg.org/mailman/listinfo/wpkg-users

[Kamil Maciejewski]

Johannes.Brix@... pisze:

> I have modified some definitions for packages, especially the "remove"
> part.
> Is it possible to force a refresh of the local wpkg.xml file without
> deleting it?
> If not, is there a simple way to delete it ?
>
> If this file is not updated, it will work with the settings for update and
> remove
> which is written there, and not with the modifications I have done on the
> server.
>
>  

They should be updated when you increase package 'revision' tag
-------------------------------------------------------------------------
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
_______________________________________________
wpkg-users mailing list
wpkg-users@...
http://lists.wpkg.org/mailman/listinfo/wpkg-users

[Rainer Meier]

Hi Johannes,

Johannes.Brix@... wrote:

> I have modified some definitions for packages, especially the "remove"
> part.
> Is it possible to force a refresh of the local wpkg.xml file without
> deleting it?
> If not, is there a simple way to delete it ?
>
> If this file is not updated, it will work with the settings for update and
> remove
> which is written there, and not with the modifications I have done on the
> server.

WPKG 1.x contains an "upgrade-before-remove" feature. This means that
you can remove a package from the profile associated to a machine. When
the machine encounters that the package is updated (you should have
increased its version when you changed the remove command part), then it
will first perform an upgrade and then execute the remove commands
(which are the changed ones then).

So do the following:
- change remove commands in your package definition
- increase package version (you just changed it above)
- either remove the package or let clients just do the upgrade

btw. you can also leave the upgrade command empty. So the upgrade will
actually not do anything on existing systems. As long as the package
checks still yield true.


br,
Rainer
-------------------------------------------------------------------------
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
_______________________________________________
wpkg-users mailing list
wpkg-users@...
http://lists.wpkg.org/mailman/listinfo/wpkg-users

[mangoo]

Kamil Maciejewski schrieb:

> Johannes.Brix@... pisze:
>> I have modified some definitions for packages, especially the "remove"
>> part.
>> Is it possible to force a refresh of the local wpkg.xml file without
>> deleting it?
>> If not, is there a simple way to delete it ?
>>
>> If this file is not updated, it will work with the settings for update and
>> remove
>> which is written there, and not with the modifications I have done on the
>> server.
>>
>>  
> They should be updated when you increase package 'revision' tag

It will start "upgrade" commands though.


--
Tomasz Chmielewski
http://wpkg.org
-------------------------------------------------------------------------
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
_______________________________________________
wpkg-users mailing list
wpkg-users@...
http://lists.wpkg.org/mailman/listinfo/wpkg-users

[Rainer Meier]

Hi Tomasz,

Tomasz Chmielewski wrote:
>> They should be updated when you increase package 'revision' tag
>
> It will start "upgrade" commands though.

Correct. However this is not a problem at all usually. Most upgrade
instructions (running the installer in silent mode again) can be run as
many times as you wish without problems.
If he wants to avoid this, then he can just remove (comment) the upgrade
command of the package. So WPKG will execute nothing, then run the
checks and find the software installed properly. After that WPKG will
write the new package node to the local settings file. So a subsequent
remove instruction will be read from the changed package definition.

br,
Rainer
-------------------------------------------------------------------------
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
_______________________________________________
wpkg-users mailing list
wpkg-users@...
http://lists.wpkg.org/mailman/listinfo/wpkg-users

[mangoo]

Rainer Meier schrieb:

> Hi Tomasz,
>
> Tomasz Chmielewski wrote:
>>> They should be updated when you increase package 'revision' tag
>>
>> It will start "upgrade" commands though.
>
> Correct. However this is not a problem at all usually. Most upgrade
> instructions (running the installer in silent mode again) can be run as
> many times as you wish without problems.

As long as your installer size / network bandwidth ratio is not too big,
YMMV ;) (think of a classroom full of laptops which all share a 54 Mbit
wireless connection).

So yes, leaving "upgrade" empty might be a wise choice.


--
Tomasz Chmielewski
http://wpkg.org

-------------------------------------------------------------------------
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
_______________________________________________
wpkg-users mailing list
wpkg-users@...
http://lists.wpkg.org/mailman/listinfo/wpkg-users

[Kamil Maciejewski]

Hello everyone, since I'm here, I'd like to ask my few questions:
1. Is there some way to use NOT EXIST as condition to install package?
Why would I want to do this? Because I'd like to have packages that
would ony upgrade installed software without doing anything when the old
version is not installed. So package should check - if the software is
not installed, it's ok, if it is installed - do an upgrade.
2. Multi profile membership - best way is to explain this is an example
- we have 3 computers and 4 packages - if we want computer #1 have
installed packages 1,2, then #2 packages 2,3, and #3 packages 1,3 - I
could create a profile for each machine, but when I have about a 100
machines? If I could split packages into few groups and can add hosts to
more than one of them it would be ok, but as far as I tried typing in
hosts.xml:

    <host name="compname" profile-id="profile" />
    <host name="compname" profile-id="other_profile" />


It only uses the first profile :(
I'd really like to have something like this working without creating
dozens of profiles (having e.g. 100 machines and 20 different packages
gives a really huge number of combinations).
-------------------------------------------------------------------------
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
_______________________________________________
wpkg-users mailing list
wpkg-users@...
http://lists.wpkg.org/mailman/listinfo/wpkg-users

[Rainer Meier]

Hi Kamil,

Kamil Maciejewski wrote:
> Hello everyone, since I'm here, I'd like to ask my few questions:
> 1. Is there some way to use NOT EXIST as condition to install package?
> Why would I want to do this? Because I'd like to have packages that
> would ony upgrade installed software without doing anything when the old
> version is not installed. So package should check - if the software is
> not installed, it's ok, if it is installed - do an upgrade.

This sounds a little curious to me.
A package contains the following types of commands:
- install
- update

If a package is already installed and the package version is increased,
then WPKG will execute the update command(s). As I understood from above
it is fine to run some update command when the package is already there.

If the package is not yet installed at all, then WPKG will run the
install command (which can be different to the update command).

> 2. Multi profile membership - best way is to explain this is an example
> - we have 3 computers and 4 packages - if we want computer #1 have
> installed packages 1,2, then #2 packages 2,3, and #3 packages 1,3 - I
> could create a profile for each machine, but when I have about a 100
> machines? If I could split packages into few groups and can add hosts to
> more than one of them it would be ok, but as far as I tried typing in
> hosts.xml:
>
>     <host name="compname" profile-id="profile" />
>     <host name="compname" profile-id="other_profile" />
>
>
> It only uses the first profile :(
> I'd really like to have something like this working without creating
> dozens of profiles (having e.g. 100 machines and 20 different packages
> gives a really huge number of combinations).

This is supported in WPKG 1.1.x milestone release. Please try the
following syntax:

<host name="compname">
        <profile id="profile" />
        <profile id="other_profile" />
</host>


Alternatively you could create a profile structure where you create a
"virtual" profile called "compname" which depends on the "profile"
profile as well as on the "other_profile" profile without adding
additional packages. The effect would be that all packages from profile
and other_profile would apply to this "compname" profile.


br,
Rainer
-------------------------------------------------------------------------
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
_______________________________________________
wpkg-users mailing list
wpkg-users@...
http://lists.wpkg.org/mailman/listinfo/wpkg-users