Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vapoursynth: restructure and add plugins #61524

Closed

Conversation

tadeokondrak
Copy link
Member

@tadeokondrak tadeokondrak commented May 14, 2019

depends on #58859

Motivation for this change

Better structure for adding future plugins

Things done

Restructure

No build changes, only package names and directories.

  • vapoursynth-mvtools -> vapoursynth.plugins.mvtools or vapoursynthPlugins.mvtools

New plugins

  • ffms2
    • built
    • tested
  • autocrop
    • built
    • tested
  • beziercurve
    • built
    • tested

previously, vapoursynth was not a python module in how most python
libraries are in nixpkgs. it would only work as part of a library or
other program, and not with its included `vspipe` program.

this fixes it by adding a new output for its python module and uses
toPythonModule to allow it to work standalone, and without conflicting
with other python packages in a nix-shell
@tadeokondrak tadeokondrak changed the title vapoursynth: restructure plugins vapoursynth: restructure plugins, init new plugins May 14, 2019
@tadeokondrak tadeokondrak changed the title vapoursynth: restructure plugins, init new plugins vapoursynth: restructure and add plugins May 14, 2019
@ofborg ofborg bot requested a review from Fuuzetsu May 15, 2019 00:29
@tadeokondrak tadeokondrak force-pushed the vapoursynth-restructure-plugins branch 2 times, most recently from e252d7f to 06865eb Compare May 15, 2019 01:01
@tadeokondrak tadeokondrak force-pushed the vapoursynth-restructure-plugins branch from 06865eb to c47afff Compare May 15, 2019 01:19
@tadeokondrak
Copy link
Member Author

closing; gonna finish this in a personal branch/overlay and then pr when finished.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant