| Summary: | building fontconfig requires network connectivity | ||
|---|---|---|---|
| Product: | fontconfig | Reporter: | Pekka Vuorela <pvuorela> |
| Component: | library | Assignee: | Akira TAGOH <akira> |
| Status: | RESOLVED FIXED | QA Contact: | Behdad Esfahbod <freedesktop> |
| Severity: | normal | ||
| Priority: | medium | CC: | akira, fontconfig-bugs, freedesktop |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Pekka Vuorela
2015-07-20 17:05:27 UTC
(In reply to Pekka Vuorela from comment #0) > As of 2.11.9x release candidates, building fontconfig requires network > connectivity in order to execute fc-blanks. That doesn't play along well > with build servers, OBS in my case. Would suggest including the resulting > header file in git / tar packages, and running the tool only when result > should be different. > > Introduced with commit d6a5cc665a1d7e91332944353e92c83ad114368c it doesn't require the network connectivity to build it from tarball. (In reply to Akira TAGOH from comment #1) > it doesn't require the network connectivity to build it from tarball. Ok, lot better already. However, on Mer/Nemo we have been moving towards having code as git submodule/subtree on the packaging repositories. I agree we should commit the built file to git, like we do fir fccase. No built files in git so far, but the data requiring to build, right. Either way works for me. Thanks. fixed. |
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.