Check whether the chmod call is needed before calling it

[Amunak]

So (as per #47) I get that you want to make the install "crash hard" when the chmod() call fails, but at least make sure that you call it only when necessary.

In the vast majority of cases the permissions are already correct but your script is crashing the whole composer install just because a different developer (user) ran it than the one who ran it the first time. When this happens on a production system while you desperately need to run all your install scripts, it's really annoying and kind of unacceptable.

You can use something akin to this:

--- /dev/null
+++ ocramius/package-versions/src/PackageVersions/Installer.php
@@ -119,7 +119,9 @@
         $io->write('<info>ocramius/package-versions:</info>  Generating version class...');
 
         file_put_contents($installPath, $versionClassSource);
-        chmod($installPath, 0664);
+        if (decoct(fileperms($installPath) & 0777) !== '664') {
+            chmod($installPath, 0664);
+        }
 
         $io->write('<info>ocramius/package-versions:</info> ...done generating version class');
     }

[Ocramius]

In the vast majority of cases the permissions are already correct but your script is crashing the whole composer install just because a different developer (user) ran it than the one who ran it the first time.

This is correct.

When this happens on a production system while you desperately need to run all your install scripts, it's really annoying and kind of unacceptable.

That means that you have no proper deployment process:

1. no deployment "owner" (user that owns the deployment dir, if any)
2. deployment process has no rollback system

As I described in #47, I can gladly fix problems when a failing automated test case is provided.

Closing as duplicate: please re-open once a test case is available.