VSRepo - the official easy plugin manager

[Myrsloik]

I have created a simple repository which can now basically install havsfunc and all its dependencies with one simple command. And a pile of other plugins and some scripts too now that I've gotten help creating more packages.

Latest version is now always bundled with VapourSynth. If you want to try out development versions or report bugs you can do it at Gihub


Usage:

vsrepo.py update
vsrepo.py install havsfunc ffms2 d2v
vsrepo.py upgrade-all
vsrepo.py installed
vsrepo.py available

You can refer to plugins/scripts in several ways. The id which is long and complicated and the namespace for plugins. For scripts it's generally the lowercase module name.

You can also add the -p switch to run it in portable mode and -f to force unknown versions of plugins to be upgraded.

Files will be installed to %APPDATA%\VapourSynth\PluginsXX and %APPDATA%\Python\X.Y\site-packages

(also known as the per user autoload directory and python's per user site directory)

All installed files will by default end up in the correct paths and instantly be usable. Make sure that the portable python directory is also the working directory when running in portable mode.

HELP CREATING MORE PLUGIN DEFINITIONS WELCOME. See the files in the local folder for examples. Report any issues.

[ChaosKing]

I see you changed the RainbowSmooth url from https://raw.githubusercontent.com/du...inbowSmooth.py to https://github.com/dubhater/vapoursy...archive/v2.zip. I tested it with the first one and it worked well. Any reason to prefer the bigger zip file?

[Myrsloik]

Originally Posted by ChaosKing

I see you changed the RainbowSmooth url from https://raw.githubusercontent.com/du...inbowSmooth.py to https://github.com/dubhater/vapoursy...archive/v2.zip. I tested it with the first one and it worked well. Any reason to prefer the bigger zip file?

Mostly that it points to a specific release/version. Pointing at master is a horrible idea that will make the hash fail as soon as a change is made to RainbowSmooth.py. If there's no release you have to at least pick a git revision and stick to that.

[ChaosKing]

Makes sense ... But I think it would be a good idea to offer both, a stable and master (latest/beta) version, since for scripts there aren't many official releases like in plugin repos. I think less then half of the scripts on github have official releases and even then, in 99% of the time, you just pick the master. At least this is my experience.

[Myrsloik]

Maybe I'll provide master/unstable labels at some point later. This is just the first version to get things started for the most common use cases. Even debugging a script with QTGMC caused greater buttpains for me just to go on the plugin/script treasure hunt for havsfunc.

[lansing]

Will it install both 32 bit and 64 bit of the plugin to each python directory respectively?

[Myrsloik]

Originally Posted by lansing

Will it install both 32 bit and 64 bit of the plugin to each python directory respectively?

No, by default it installs the same bitness as the python you're running it with. You can control which one is installed with "-t win32" or "-t win64"

[lansing]

Shouldn't the Vapoursynth plugin path be inside "program files (x86)/vapoursynth"? Why is it pointing to %appdata% instead?

[Are_]

Just a wild guess

Originally Posted by Myrsloik

Files will be installed to %APPDATA%\VapourSynth\PluginsXX and %APPDATA%\Python\X.Y\site-packages

(also known as the per user autoload directory and python's per user site directory)

[foxyshadis]

Originally Posted by lansing

Shouldn't the Vapoursynth plugin path be inside "program files (x86)/vapoursynth"? Why is it pointing to %appdata% instead?

In default use, it won't have permissions. I have mine in a custom folder with liberal permissions, but I'm pretty sure Myrsloik's intention is having a well-known folder with plugins and scripts for better support. Customize away if you support yourself!

[Myrsloik]

Originally Posted by foxyshadis

In default use, it won't have permissions. I have mine in a custom folder with liberal permissions, but I'm pretty sure Myrsloik's intention is having a well-known folder with plugins and scripts for better support. Customize away if you support yourself!

1. Permissions. Default global directories need administrative rights and that's a problem.
2. Why do you feel this need to stuff everything into program files where it shouldn't be?
3. It's a horrible idea to change state of plugins for all users in a true multi-user environment. Just saying.

[Myrsloik]

Updated version posted, now has 46 plugins and scripts in total. Feel free to request what should be added next or create the definitions yourself.

[Myrsloik]

Updated to test5 in the first post, it now has various small bugfixes and simple caching to make it work faster when many things are being installed at once.

About 10 more packages since yesterday too. Keep the submissions coming and we'll have a complete package system created in under one week!

(it's already quite complete so start using havsfunc and vsTAAmbk without having to go on a treasure hunt)

[Myrsloik]

The daily update. Now we're up to 67 plugins and scripts. I'm surprised there hasn't been more feedback yet. Is it too sunny outisde?

[lansing]

There can be a command to list all available plugins and their installation status, and there can also be a command to just install all plugins.

[Myrsloik]

Originally Posted by lansing

There can be a command to list all available plugins and their installation status, and there can also be a command to just install all plugins.

Listing all available ones, sure. Installing all plugins is just ridiculous though.

[ChaosKing]

Originally Posted by Myrsloik

About 10 more packages since yesterday too. Keep the submissions coming and we'll have a complete package system created in under one week!

One Problem ist that not every git repo has also a release aka binaries, only source code...

I hope this motivates people to provide some binaries as well.

[Myrsloik]

Originally Posted by ChaosKing

One Problem ist that not every git repo has also a release aka binaries, only source code...

I hope this motivates people to provide some binaries as well.

Yes, it really annoys me when people can't be bothered to make releases and put binaries on github.

[lansing]

Originally Posted by Myrsloik

Installing all plugins is just ridiculous though.

Why is that? It gives an option to people who are new or people who don't really care about customization a hassle-free installation.

[Myrsloik]

Originally Posted by lansing

Why is that? It gives an option to people who are new or people who don't really care about customization a hassle-free installation.

It's a waste of bandwidth and a recipe for potential problems. There's a reason "apt-get install-all" is not a thing in linux...