tool standalone vpm
Credits: LibGit2Sharp, PowerArgs, SharpCompress, Fody Weavers, Fody Costura
Documentation is at https://github.com/microdee/vpm
Now you can browse and install packs from the VPDB pack repository with ease!
(* available through https://vvvvpm.github.io/ )
I figured since the actual files are already put into a subfolder, I might as well just put all the DLL's there and not weave them into main exe. This also allows to use all referenced assemblies in the installation script
and loading spinners for UX shenanigans
Powered by a CefSharp control
this means pack developers can reference System and some basic namespaces of it with the using statement
see related news article here: introducing-vpm-a-vvvv-package-manager.
(for older version)
Interesting but still very much alpha it seems. Would really need to have some version info for packs.
Seems you can have arbitrary c# code in a .vpack? Powerful but also seems a bit like handing over your keys to your house to the author from a security perspective but with curated package repo it might be ok.
If you use the latest_alpha packs to install vvvv it seems like it will just copy new files over an existing vvvv directory with no cleaning up of files not used by a newer version?
@beyon: good and valid points, responses:
Versioning: I've tried to implement versioning at some point and I found it would introduce more brain-cancer than it would have supposed to solve. Especially in situations where inside the dependency tree 2 different versions of the same pack is referenced. For now if a pack requires an older version of an other pack it's simpler to script its custom fetching than having to keep in mind an xml infrastructure for that thing. Also I think "do you want to overwrite?" prompt is the easiest way currently for everyone.
Scripting: yes arbitrary C# code. So well as with any executable file on the internet download only from trusted sources. vvvv community is so small though that a malacious script wouldn't live long on the website or on github. On the other hand vpm is not elevated if the script would try to access sensitive areas vpm would just throw an access denied exception. I can add a dialog box which can list the scripts to be executed then user can decide if they're harmless. On curated package repo: https://github.com/vvvvpm/vpdb
On deleting files: I'd leave that for the scripts to decide as well. I can add a user prompt in the vvvv install script if they want to delete old files (move to recycle bin) before installation.
super interesting! as vpm doesnt require vvvv to be installed beforehand, would it make sense to include the vvvv dependencies of setup.exe in the vpm package of vvvv? or would that require special handling?
no, that absolutely makes sense to do, only I didn't have the willpower to do it yet
I just tried vpm
for some reason it's downloading to the wrong directory. It's placed the .vpm and packs folder in the parent of the vvvv directory. I registered the correct vvvversion
hmm strange. what's your vvvv's path?
ok let me test it with directory name with spaces in it
alright tested it and spaces work. are you using latest version?
Is i tpossible to target an arbitrary version of vvvv when installing a pack?
well yeah via scripting but you should prompt the user either during licence page or with a console question because it can break stuff for other packs. you can extract a download link from the download section and use that to download the vvvv in the C# script, then in the script just extract and copy + overwrite into the vvvv folder.
or if you want latest alpha just add the vvvv updater vpack from vpdb to the dependencies
anonymous user login