Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 252940

vadk:PackagesToRemove--How does that work?

$
0
0

I am running into unexpected behaviour using (or trying to use) vadk:PackagesToRemove.  Has anyone had any success with this section?  Or does anyone have any insight to share?

 

I name a PackageGroup that contains package X in JEOSSection_Type/OSPackages, and then list X in PackagesToRemove.  With this declaration, I expect the named group to be installed and then the package X to be uninstalled, but X is not uninstalled and appears in .../status/packages.txt

 

Any help/explanation here would be much appreciated.  Am I misinterpreting PackagesToRemove?  Is there a problem with PackagesToRemove?  Or?

 

For context, I am running VMware Studio 2.5.0.0 Build 387333 and installing an Oracle Linux 6.3 guest (based on the included RHEL 6.0 profile).  The relevant portion of the build profile is:

 

<Section xsi:type="vadk:ApplicationSection_Type">

...

    <vadk:PackagesToRemove>
      <vadk:Package vadk:name="NetworkManager-gnome"/>
      <vadk:Package vadk:name="NetworkManager"/>
    </vadk:PackagesToRemove>

...

</Section>

...

<Section xsi:type="vadk:JEOSSection_Type">

...

    <vadk:OSPackages>

...

      <vadk:PackageGroup vadk:value="basic-desktop"/>
...

   </vadk:OSPackages>

...
</Section>

...

</Section>

 



Viewing all articles
Browse latest Browse all 252940

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>