ariadne
/
pkgconf
3
6
Fork 4
Code Issues 6 Pull Requests 2 Projects Releases 2 Wiki Activity

Created Roadmap (markdown)

master
nenolod 2012-07-23 23:17:50 -07:00
parent ebc93ea97c
commit eb2baf3558
1 changed files with 30 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
Roadmap.md Normal file

@ -0,0 +1,30 @@
## Short-term goals
### Legacy `pkg-config` compatibility.
Find and support any remaining pkg-config extensions that are actually used by build infrastructure. The best way of accomplishing this is by running mass tinderbox builds until we have no regressions against pkg-config itself.
Some things should be fixed in pkgconf, other things should be fixed in the upstream sources because they do stupid things they shouldn't be doing, like `pkg-config --version` to query the pkg-config API level.
Several people are helping with this, such as flameeyes (Gentoo) and bapt (FreeBSD).
Any incompatibility on UNIX platform is a regression and should be considered a bug.
### Advocacy with distributions
In order to succeed with our longer-term goals, we need distributions to actually switch their pkg-config implementation in the stack. Once that is done, we can incrementally work on future goals.
The gears on this are starting to churn. People are seeing the immediate benefits of changing the pkg-config implementation to `pkgconf`:
* No license issues at all (`pkgconf` is effectively the closest thing you can get to public domain under Oklahoma law).
* Reduced circular dependencies in the toolchain stack.
* Support for features distributions need which are unavailable in pkg-config.
* Strong test-driven development including strong testing against prior regressions.
If you want to help convince distributions to switch, those are some good advocacy points to use.
## Longer-term goals (in order)
### libpkgconf library
Allow other frontends to the pkg-config data, this is a critical component for future plans.