Difference between revisions of "DeveloperWiki:Pacman Roadmap"

From ArchWiki
Jump to: navigation, search
(Potential Release Schedule)
(New Feature Ideas)
Line 26: Line 26:
'''Flyspray:''' {{bug|28014}}
'''Flyspray:''' {{bug|28014}}
===Package Verification===
'''Idea:''' Verify the integrity of files from installed packages
'''Flyspray''' {{bug|11091}}
'''Status:''' in git master - requires libarchive support for md5/sha256 checking
Line 58: Line 50:
'''Development branch:''' https://github.com/moben/pacman/tree/optdep
'''Development branch:''' https://github.com/moben/pacman/tree/optdep
===Makepkg VCS packaging overhaul===
'''Idea:''' The current handling of SCM PKGBUILDs in makepkg is a mess and needs many improvements. See [[User:Allan/Makepkg_VCS_overhaul|here]] for a more detailed description.
'''Flyspray:''' (many - see above link)
'''Status:''' in git master
===Parallel operations===
===Parallel operations===
Line 73: Line 58:
'''Mailing List:''' https://mailman.archlinux.org/pipermail/pacman-dev/2011-February/012466.html, https://mailman.archlinux.org/pipermail/pacman-dev/2011-February/012508.html
'''Mailing List:''' https://mailman.archlinux.org/pipermail/pacman-dev/2011-February/012466.html, https://mailman.archlinux.org/pipermail/pacman-dev/2011-February/012508.html
===Pacsave numbered backups===
'''Idea:''' If .pacsave already exists, move to .1, etc.
'''Flyspray:''' {{bug|24192}}
'''Mailing List:''' https://mailman.archlinux.org/pipermail/pacman-dev/2011-August/013981.html
'''Status:''' in git master
===Iterator interface for databases===
===Iterator interface for databases===

Revision as of 04:57, 12 April 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.

Pacman 4.2


  • (Nothing)


  • (Nothing)

New Feature Ideas

Package Signing - Polishing

Idea: Tidy up our current implementation of package signing.

Flyspray: FS#28014


Idea: Pacman should have hooks to perform common tasks. See here for a more detailed description.

Flyspray: FS#2985

Mailing List:

Development branch: Not started

Optdepend Handling

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)

Mailing List: https://mailman.archlinux.org/pipermail/pacman-dev/2011-August/013961.html

Development branch: https://github.com/moben/pacman/tree/optdep

Parallel operations

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.

Flyspray: (None)

Mailing List: https://mailman.archlinux.org/pipermail/pacman-dev/2011-February/012466.html, https://mailman.archlinux.org/pipermail/pacman-dev/2011-February/012508.html

Iterator interface for databases

Idea: Provide an iterator interface for databases, especially those with 'files' entries, to keep memory usage in check.

Mailing List: https://mailman.archlinux.org/pipermail/pacman-dev/2011-July/013816.html

Future Release Plans

See flyspray roadmap