| Summary: | Check for availability of 'pyparsing' during configure time | ||
|---|---|---|---|
| Product: | Spice | Reporter: | David Jaša <jasa.david> |
| Component: | spice-gtk | Assignee: | Spice Bug List <spice-bugs> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
build output
potential way of handling this |
||
unfortunately, configure cannot be told to check for non-dist dependencies. Iow, we don't check for pyparsing from the tarball configure, as it's not required. The git build depedencies are leasted in README. Created attachment 47230 [details] [review] potential way of handling this Something like this could be done to fail more gracefully when pyparsing is missing in a git checkout. I don't get why this is WONTFIX. This was pretty annoying to debug while packaging 0.12.101 for Mageia. Tarballs are supposed to ship the files pyparsing generates, but this got broken recently (I think during the switch to git submodules). But 1 year after, I still think a patch like the one in this bug would be useful. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 46904 [details] build output SSIA version: from git://gitorious.org/spice-gtk/spice-gtk.git , fetched 2011-05-19.