Difference between revisions of "DeveloperWiki:Pacman Roadmap"
|Line 14:||Line 14:|
Revision as of 00:55, 30 June 2013
This page does not provide a traditional roadmap. Pacman releases are generally made after a major feature has been added and these get added in the order that patches are contributed.
Instead, this page provides a brief overview of major features being discussed for future inclusion in pacman. This does not represent a complete list of all areas of pacman development (or even areas currently being developed...). All discussion about pacman development should take place on the pacman-dev mailing list.
Potential Release Schedule
This is not a for sure list by any means. This is simply to keep the main development team focused on a given release and what needs to be polished before we can push a major version out the door.
- directory as symlink support removal
New Feature Ideas
Package Signing - Polishing
Idea: Tidy up our current implementation of package signing.
Idea: Pacman should have hooks to perform common tasks. See here for a more detailed description.
- https://mailman.archlinux.org/pipermail/pacman-dev/2010-July/011441.html (first of set of four)
Development branch: Not started
Idea: Currently optdepends in pacman serve no purpose other than informational. It would be useful if these could be handled in a similar fashion to regular dependencies for many operations. See here for a more detailed description of what is currently being implemented.
Flyspray: FS#12708 (and others)
Development branch: https://github.com/moben/pacman/tree/optdep
Idea: Some things libalpm does are embarrassingly parallel, make it happen. Also, simply allow the library to be used in multithreaded environments even if we do not do parallel stuff on our own- namely DB loading stuff needs to be protected.
Iterator interface for databases
Idea: Provide an iterator interface for databases, especially those with 'files' entries, to keep memory usage in check.
Future Release Plans
See flyspray roadmap