[wpkg-users] [Bug 56] New: individual packages should have "force" flag

bugzilla-daemon at wpkg.org bugzilla-daemon at wpkg.org
Fri Jan 26 12:12:33 CET 2007

Please reply using this URL only: http://bugs.wpkg.org/show_bug.cgi?id=56

           Summary: individual packages should have "force" flag
           Product: WPKG
           Version: 0.9.10
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: wpkg.js
        AssignedTo: mangoo at mch.one.pl
        ReportedBy: mangoo at mch.one.pl
         QAContact: wpkg-users at lists.wpkg.org

Individual packages should have ability to set the "force" flag (disabled by

        name="ALBIS Demoversion 8.40"
<check type="file" condition="exists" path="C:\aowdemo\a_test\albis840.txt" />
<check type="file" condition="exists" path="C:\aowdemo\z_test\albis840.txt" />

Its effect should be the same as using the /force flag in wpkg.js command line -
but only for that given package.

some Windows software is still written as if it was DOS, Windows 3.1 or Windows
95, and requires write access to the directory where it was installed. This
means, any user can potentially change or delete such files, or even the whole
With that flag, we would be sure WPKG checks if the package is installed correctly.

Configure bugmail: http://bugs.wpkg.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

wpkg-users mailing list
wpkg-users at lists.wpkg.org

More information about the wpkg-users mailing list