Helper functions to simplify writing setup scripts that modify VenusOs functionality. The package includes automatic reinstallation of the package after a VenusOs update.
I just released a major update to SetupHelper
This version includes conflict checking along with some bug fixes. Consult the change log for details.
Conflict resolution is based on dependencies defined for a package,
plus a check for any already modified files that the package would also modify.
The dependencies are defined in the packageDependencies file and specify
what other packages need to be installed or uninstalled before allowing the package install.
The package author is responsible for creating the dependencies.
The file conflict checks every file a package will install. If the file has already been modified,
a check is made to a .package file that specifies which package did the modification.
If that package is not "this" package, then the offending package needs to be uninstalled.
Note that file conflict checks require install with SetupHelper v7.0 or later, so if you want this to work
you need to uninstall each package then install it again.
The Package Manager menus indicate package conflicts an the Package editor menu provides a way to show
the details of the conflict. If the conflicts can be resolved, the Proceed button starts download, install and uninstall operations
needed to allow "this" package to be installed. If all conflicts are resolved, the Install button becomes active.
If you have any problems or questions about this new functionality, please post to this issue.
If you need to revert to a previous version of SetupHelper, set the branch/tag to v6.12 which was the previous released version.
I just released a major update to SetupHelper This version includes conflict checking along with some bug fixes. Consult the change log for details.
Conflict resolution is based on dependencies defined for a package, plus a check for any already modified files that the package would also modify.
The dependencies are defined in the packageDependencies file and specify what other packages need to be installed or uninstalled before allowing the package install. The package author is responsible for creating the dependencies.
The file conflict checks every file a package will install. If the file has already been modified, a check is made to a .package file that specifies which package did the modification. If that package is not "this" package, then the offending package needs to be uninstalled.
Note that file conflict checks require install with SetupHelper v7.0 or later, so if you want this to work you need to uninstall each package then install it again.
The Package Manager menus indicate package conflicts an the Package editor menu provides a way to show the details of the conflict. If the conflicts can be resolved, the Proceed button starts download, install and uninstall operations needed to allow "this" package to be installed. If all conflicts are resolved, the Install button becomes active.
If you have any problems or questions about this new functionality, please post to this issue.
If you need to revert to a previous version of SetupHelper, set the branch/tag to v6.12 which was the previous released version.