Posted November 19, 2017
Kalanyr: I think I've preserved one for one backwards compatibility* (assuming you use Windows / English / Standalone installers. You may have to make some minor adjustments otherwise).
I've added some extra functionality that might reduce some of the need for your batch files depending what they do though (it's generally more fine grained control of exclusion / inclusion). Have a look at the help.
*The commands may do some extra stuff like logging, but they should carry out their original purpose and side effects should be relatively minor.
I also think this update will fix that outstanding issue where Python3 no longer worked for my fork after the last update (sorry about that Python3 peeps). I'm just testing that at the moment.
Edit - Yes, it does fix the Python3 issue. Not however that Python2 manifest files probably are not compatible with python3 and may need to be regenerated (chances are excellent that a Python2 manifest contains a size that was a Long in python2 (encoded as size: xxxxxxL) , python3 doesn't have longs (since the long and int types have been unified). Unfortunately Python3 can't recognize a Python2 Long stored in manifest and treat it as an Int. Python2 on the other hand transparently turns any Long sized Int into a Long automatically). So basically don't use Python2 / Python3 interchangeably on the same manifest if you want to avoid grief.
Also, the readme on yours looks identical to the readme on the original. How do I know what command flags change and their uses?I've added some extra functionality that might reduce some of the need for your batch files depending what they do though (it's generally more fine grained control of exclusion / inclusion). Have a look at the help.
*The commands may do some extra stuff like logging, but they should carry out their original purpose and side effects should be relatively minor.
I also think this update will fix that outstanding issue where Python3 no longer worked for my fork after the last update (sorry about that Python3 peeps). I'm just testing that at the moment.
Edit - Yes, it does fix the Python3 issue. Not however that Python2 manifest files probably are not compatible with python3 and may need to be regenerated (chances are excellent that a Python2 manifest contains a size that was a Long in python2 (encoded as size: xxxxxxL) , python3 doesn't have longs (since the long and int types have been unified). Unfortunately Python3 can't recognize a Python2 Long stored in manifest and treat it as an Int. Python2 on the other hand transparently turns any Long sized Int into a Long automatically). So basically don't use Python2 / Python3 interchangeably on the same manifest if you want to avoid grief.