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

Missing dependencies of extensions should not prevent execution #65

Closed
akerbos opened this issue Oct 11, 2015 · 0 comments
Closed

Missing dependencies of extensions should not prevent execution #65

akerbos opened this issue Oct 11, 2015 · 0 comments
Assignees
Labels
Milestone

Comments

@akerbos
Copy link
Collaborator

akerbos commented Oct 11, 2015

Currently, some extensions specify essential dependencies. While they are essential to their own execution, they are not for the whole program. For example, missing gnuplot does not prevent most documents from being compiled.

  1. Separate dependencies by source; only dependencies of the core should always block execution.
  2. Check core dependencies and what can be figured out from CLI parameters at startup.
    For example, engine and log mode are known then.
  3. Check extension dependencies when they are to be run. Don't abort everything; just skip the extension.

On a side-note, dependencies from engines don't seem to show up in the --dependencies dump?

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

No branches or pull requests

1 participant