| Summary: | Yelp use of unstable-interface librarian | ||
|---|---|---|---|
| Product: | Rarian | Reporter: | Daniel Macks <dmacks> |
| Component: | General | Assignee: | Don Scorgie <Don> |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | CC: | dmacks |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | http://bugzilla.gnome.org/show_bug.cgi?id=466466 | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Daniel Macks
2007-08-13 20:45:12 UTC
Seems like the interface is stabilizing, yes? You don't have to freeze it permanently forever into the future, just declare that the current state is ABI 1 or whatever, and then adjust the interface aging and foward/backward-compatibility flags when the interface changes. That way other packages can know what they're dealing with, and maintainers for various package-managers don't go insane. Rarian is API-unstable until 1.0. Don't know when that will be, but each minor series until then is liable to API changes. In current SVN Head, I've defined an error unless I_KNOW_RARIAN_0_8_IS_UNSTABLE is defined: #ifndef I_KNOW_RARIAN_0_8_IS_UNSTABLE #error Rarian is unstable. To use it, you must acknowledge that #endif This is (ironically) one of the lessons I've learned while writing rarian. I don't really know about libtool versioning, but I will get it sorted properly during this release cycle. |
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.