http://bugzilla.wpkg.org/show_bug.cgi?id=259 Summary: Feature Request - configuration elements for common operations Product: WPKG Version: other Platform: PC OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: wpkg.js AssignedTo: mangoo at wpkg.org ReportedBy: peterhoeg at gmail.com QAContact: wpkg-users at lists.wpkg.org You will often find (and write) repetitive setup for common operations such as copying and deleting files/directories. We are shelling out for a number of actions and often end up with stuff like cmd='%COMSPEC% /c IF EXIST "some random file"'. Some actions such as copying need to happen in a certain way to ensure the output buffer is not filled up which means we have to remember to pass /Q to XCOPY or divert stdout to NUL. All that is ugly and error prone. It would be very elegant if we could define keywords for those actions and have WPKG simply pick the best way to handle it safely behind the scene. As an example for copying we make sure no output is generated or based on the current logging sections divert the output to the standard log file. The most common cases are: 1) copy one or more files from A to B and ensuring no output is generated 2) delete one or more files/directories Syntax suggestions: 1) <install type='copy' source='%SOFTWARE%\SomePackage\*.dll' target='%WINDIR%' /> 2) <remove type='file' target='%PROGRAMFILES%\VideoLAN' ignoreerrors=true /> Case 1 could even be extended to look for robocopy and use that if found or otherwise fall back to XCOPY. And making sure to pass the proper parameters in both cases. Any thoughts? -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |