Package Tool Workflows

%3CLINGO-SUB%20id%3D%22lingo-sub-2312910%22%20slang%3D%22en-US%22%3EPackage%20Tool%20Workflows%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2312910%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20has%20been%20mentioned%20before%2C%20but%20with%20Shared%20Package%20Containers%20finally%20being%20a%20thing%2C%20it%20becomes%20more%20important...%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOne%20thing%20that%20we'd%20like%20to%20see%20is%20workflows%20in%20the%20packaging%20tool%20that%20involve%20previously%20created%20packages.%26nbsp%3B%20There%20are%20threeimportant%20scenarios%20of%20interest%3B%20we%20use%20these%20a%20lot%20in%20App-V%20Packaging%3A%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3E%26nbsp%3BUpgrading%20an%20existing%20package%20by%20using%20an%20installer.%3C%2FLI%3E%0A%3CLI%3ECreate%20a%20plugin%20package%20that%20has%20an%20installer%20that%20requires%20the%20main%20package%20to%20be%20installed%20first.%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3ECreating%20a%20package%20for%20Shared%20Package%20Containers.%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EIn%20both%20cases%2C%20you%20want%20to%20unpackage%20an%20existing%20package%20(prior%20to%20monitoring%20mode)%20to%20restore%20it%20into%20a%20system%20just%20as%20it%20had%20been%20originally%20installed%20and%20captured.%26nbsp%3B%20In%20the%20App-V%20Sequencer%20this%20is%20exposed%20as%20%22export%20to%20local%20system%22%20as%20a%20menu%20and%20as%20part%20of%20the%20%22upgrade%22%20and%20%22plugin%22%20scenario%20workflows.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EIt%20is%20likely%20that%20packagemgr%20has%20most%20of%20the%20required%20functionality%2C%20but%20what%20would%20make%20this%20useful%20is%20to%20embed%20the%20functionality%20right%20into%20the%20Packaging%20Tool%20workflows.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
MVP

This has been mentioned before, but with Shared Package Containers finally being a thing, it becomes more important...

 

One thing that we'd like to see is workflows in the packaging tool that involve previously created packages.  There are threeimportant scenarios of interest; we use these a lot in App-V Packaging:

  1.  Upgrading an existing package by using an installer.
  2. Create a plugin package that has an installer that requires the main package to be installed first.
  3. Creating a package for Shared Package Containers.

 

In both cases, you want to unpackage an existing package (prior to monitoring mode) to restore it into a system just as it had been originally installed and captured.  In the App-V Sequencer this is exposed as "export to local system" as a menu and as part of the "upgrade" and "plugin" scenario workflows.

 

It is likely that packagemgr has most of the required functionality, but what would make this useful is to embed the functionality right into the Packaging Tool workflows.

1 Reply

Hi @TIMOTHY MANGAN These are all great suggestion for us to look into.