I have or had a problem with Acrobat. I have 3 profiles all of which inherit from eachother their packages. Eg: SOE -> Laptop -> Machine. I have 4 types of acrobat writers, Elements 6, Standard 6, Standard 8 and Pro 8. Elements was defines at the SOE level, early on. Rather than elevate Elements to machine level so I could implement Conflicts between the 4 type I decided to create a virtual based package, AcrobatWriter The check is defined as Elements or Std 6 or Std 8 or Pro 8 The command is simply to install Elements 8 No uninstall exists. At the machine level I add the packages for Pro 8, std 8 and std 6 as required The install command is 1st, uninstall elements6 then install std 8. Now this is a bit messy, however I had the thought that if packages could inherit other packages automatically as well as depend or Supercedes packages as priority you could do a better job than implementing virtual packages. Eg: Acrobat Pro 8 package Supercedes Writer package. Writer inherits Elements and reader 6 so Elements and reader 6 package is uninstalled.
------------------------------------------------------------------------- wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ _______________________________________________ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
