Suggestion for Improvement: Bundle Creation

[neckatskin]

Hello,

I've been testing your WAPT solution for a while now, and despite a minor issue with repository replication (which I hope will be resolved soon ), I've been very impressed with your solution.

However, there are a few areas where the software could be improved, particularly when creating bundles:

- When creating bundles, the software deploys the applications in the order they appear in the bundle. This order can be important: for example, if a piece of software takes a while to deploy, you can take advantage of the time to perform a (complex) post-configuration of another application, such as creating an Outlook account. Currently, it's impossible to change the order of the applications within a bundle; this requires recreating the entire bundle. It would be useful to be able to change the order of the applications without having to recreate the bundle (especially useful when there are 20-30 applications in a bundle).
Furthermore, modifying a bundle automatically increments its version number by 1, even if it's just a change to the bundle description, without any option for the user to modify it manually. I think it would be beneficial to give users control over this version numbering: for example, allowing for more specific details like "1.2" or "2.1.0".

Please feel free to share your thoughts on this,


NeckAtSkin.

[sfonteneau]

Hello neckatskin,

Thank you for your feedback!

Regarding your comment, I'm not sure I fully understand the problem.
The Dependency System allows you to choose an installation order.

As for the "bundle," the packages are not re-downloaded each time.

For example: You have an office suite that contains LibreOffice and Microsoft Office. This suite is deployed on a workstation in the accounting department.

You decide to add Firefox to the office suite. The accounting workstation will therefore download the office suite package (3KB) and the Firefox package (which is the missing dependency). The LibreOffice and Microsoft Office packages will not be re-downloaded since the dependency has already been addressed.


Regarding manual versioning, you can already do this by enabling the advanced options in the console.

Simon

[neckatskin]

Yes, indeed, you can determine an installation order using dependencies, but I see this function more as a prerequisite: a piece of software that needs another piece of software to be installed and/or function. I just wanted to highlight the fact that you can modify the installation order without using this dependency system; I'm nitpicking over nothing. It's just a minor detail. I understood that the packages aren't re-downloaded; I was just saying that it was impossible to change the order of the packages without using dependencies, but anyway, as I said before, it's just splitting hairs.

On the other hand, I don't understand how to edit the versioning on the bundle. When I switch to advanced mode in the bundle editor, the version remains grayed out and cannot be modified. Is this a feature subject to a commercial license?