[wpkg-users] [Bug 53] One Host, several Profiles

[bugzilla-daemon at bugzilla.wpkg.org]

http://bugzilla.wpkg.org/show_bug.cgi?id=53


Falko Trojahn <ftrojahn at smi-softmark.de> changed:

           What    |Removed                     |Added

                 CC|                            |ftrojahn at smi-softmark.de




--- Comment #7 from Falko Trojahn <ftrojahn at smi-softmark.de>  2007-11-20 10:42:34 ---
I vote for this bug since it would need much less profiles
for managing a location. I accept your opinion, Rainer, but
I'd like to show the following real world example.

Each additional program leads to one or a combination of
several profiles to achieve it:

<host name="hostname1" profile-id="rati01wrar" />
...

    <profile id="rati01">
        <depends profile-id="default" />
        <package package-id="acrobat8" />
        ...
        ...
    </profile>

    <profile id="rati01ge">
        <depends profile-id="rati01" />
        <package package-id="googleearth" />
    </profile>


    <profile id="rati01wrar">
        <depends profile-id="rati01" />
        <package package-id="winrar" />
    </profile>

    <profile id="rati01vis">
        <depends profile-id="rati01" />
        <package package-id="msvisio2003" />
        <package package-id="msvisio2003-kb923272" />
        <package package-id="msvisio2003-kb924424" />
        <package package-id="msvisio2003-kb920813" />
    </profile>

    <profile id="rati01proj">
        <depends profile-id="rati01" />
        <package package-id="msproject2003" />
    </profile>

    <profile id="rati01geproj">
        <depends profile-id="rati01ge" />
        <package package-id="msproject2003" />
    </profile>

    <profile id="rati01visproj">
        <depends profile-id="rati01vis" />
        <depends profile-id="rati01proj" />
    </profile>

I know that wpkg-web handles this by using one profile for each client.
But that way we would not need profiles at all - you could assign packages
directly to the client.

Using several profiles with one host like in the example from above would look
like this:

<host name="rati.+" profile-id="rati01" />

<host name="ratiws-0108" >
         <profile profile-id="rati01wrar" /> 
         <profile profile-id="rati01vis" /> 
         <profile profile-id="rati01ge" /> 
     </host>

<host name="ratiws-0153" >
         <profile profile-id="rati01vis" /> 
         <profile profile-id="rati01pro" /> 
         <profile profile-id="rati01ge" /> 
     </host>

So, I have the information there I need it: near the host.
I used a syntax like that from profiles, 


<profile id="rati01vis">
        <package package-id="msvisio2003" />
        <package package-id="msvisio2003-kb923272" />
        <package package-id="msvisio2003-kb924424" />
        <package package-id="msvisio2003-kb920813" />
    </profile>

<!-- for sure googleearth can depend from rati01 profile, too -->
<profile id="rati01ge">
        <depends profile-id="rati01" />
        <package package-id="googleearth" />
    </profile>

<profile id="rati01proj">
        <package package-id="msproject2003" />
        <package package-id="msproject2003-kb837240" />
        <package package-id="msproject2003-kb887620" />
        <package package-id="msproject2003-kb837240" />
    </profile>

I don't know if it is really difficult to implement it in the new release -
it would have been easier, if we took this into account earlier.
We could use another syntax (according to the above example), too,
if this is better to implement:

<host name="rati.+" profile-id="rati01" />

<host name="ratiws-0108" profile-id="rati01wrar" />
<host name="ratiws-0108" profile-id="rati01ge" />
<host name="ratiws-0108" profile-id="rati01vis" />

Existing: go through hosts file, read in a profile for a host, use it.
Could change to:
Go through hosts file, read in a profile for a host, 
add next profile to the host ... use it.

Just my 2c. I'll attach the changes from Hannes as a patch against 0.9.10, too.


-- 
Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


wpkg-users mailing list
wpkg-users at lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users