| Summary: | Disable automagicness on Farsight and Glib | ||
|---|---|---|---|
| Product: | Telepathy | Reporter: | Tomáš Chvátal <tomas.chvatal> |
| Component: | tp-qt | Assignee: | Telepathy bugs list <telepathy-bugs> |
| Status: | RESOLVED NOTABUG | QA Contact: | Telepathy bugs list <telepathy-bugs> |
| Severity: | normal | ||
| Priority: | medium | CC: | ollisal |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: | automagicness.patch | ||
|
Description
Tomáš Chvátal
2011-04-20 05:37:23 UTC
Why would you want to disable essentially the entire unit test suite? That's what disabling tp-glib use does, with no effect to the actual library binary. OK, I'm resolving this as not a bug. I'll reiterate: the farsight and glib bits don't have *any* effect on the main library binary or headers. They don't cause any "bloat" increase in it, which I guess is your main concern. tp-glib, and qt support for the glib mainloop are only used for building and running the unit tests. Running them if you have the required bits installed doesn't hurt any - rather only helps catch regressions. Then again if your ebuild isn't running make check, they have no effect whatsoever. Farsight causes a single pkgconfig file, a single header (Farsight/channel.h) and a tiny library (telepathy-qt4-farsight) to be built and installed, which combined takes around 1sec out of the several minutes for the entire library build. Your ebuild can use the farsight use flag (if you have something like that) to avoid installing them from the build sandbox instead, if you're concerned with filesystem usage. That issue is still valid for 0.7.0, please at least have some look on it. Thank you I know it's there, as we haven't changed a thing. However, please respond to my queries about what kind of drawbacks does automatically picking up them cause, so that we can look into ways to mitigate them. |
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.