Rémy

Unfortunately this is blocking us from updating to php 7.3

I have to clarifya bit more, implementing travelling dirs would take place in the scoop update command. But testing modified manifests would take the install path, ignoring the already installed...

Thanks for the inputs ## Persistent data Using conjunctions sounds great. I tested it with the mariadb database content and it works great! There is a config option `NO_JUNCTIONS`, it...

Unfortunately conjunctions are causing problems, not every program likes them 😞 As example nodejs breaks, fails at `npm update -g` ``` scoop persist *$% = .\bin\scoop.ps1 install nodejs Loading node-v7.7.3-x64.msi...

That seems to be a different problem. `npm cache clean` does not affect the problems. As soon I use a conjunction for the node_modules directory strange things start to happen....

Yes, that would be sad. I didn't test, but I think we will have the similar problems with elasticsearch as of #1202 Me neither, but I heard on Linux some...

It works! Thanks 👍 I had to changed the [npm prefix](https://docs.npmjs.com/files/folders) to install the binary links into the data directory else they would not survive an update. 912fbe896761e3955df3b9d1a69bb6d2c2c22c46 Better ideas...

Has anyone experience with python and pip? I can't figure out what needs to be persistent. @lukesampson I merged your commit and rebased my persist branch upon the current master...

That won't work. The scripts are outside of the node_modules directory. With the default config they would be at the same level as the `node.exe`. I just realised we do...

I changed `data` to `persist` 36e61b54f920e18868eaee1145ce6e11ee16e8b5 I don't know what you mean with `$persist_link`, the `$persist_dir` variable is the only introduced variable outside the `persist_*` functions.