Difference between revisions of "DeveloperWiki:Pacman Roadmap"

From ArchWiki
Jump to: navigation, search
(Pacsave numbered backups)
(this page is for major feature listings)
Line 84: Line 84:
  
 
'''Mailing List:''' http://mailman.archlinux.org/pipermail/pacman-dev/2011-August/013981.html
 
'''Mailing List:''' http://mailman.archlinux.org/pipermail/pacman-dev/2011-August/013981.html
 
===Pacman recovery tool===
 
 
'''Idea:''' If for any reason pacman is break or any important (/etc/pacman.conf ; /etc/pacman.d/mirrorlist ; /etc/makepkg.conf) are unreadable, a script or a tool or any mechanism for reintall or recover tose break part, this is usefull if for a filesystem corruption or accidentally or a bad upload is efectuated and pacman are unable to run, this can reinstall pacman ain the old (or any other uggested) way
 
 
'''Flyspray:''' [https://bugs.archlinux.org/task/29865 FS#29865]
 
  
 
===Iterator interface for databases===
 
===Iterator interface for databases===

Revision as of 14:16, 6 June 2012

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.


Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어


External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی

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.1

Queued:

  • Improved optdepend handling
  • Pacsave non-overwriting file renames

Maybes:

  • Color output
  • Parallel operations (mainly integrity checking and package loading)
  • Package/Transaction/File Hooks

New Feature Ideas

Package Signing

Idea: Package signing would make pacman transactions more secure. See Pacman package signing for a more detailed description, as well as DeveloperWiki:Package Signing Proposal for Pacman.

Wiki: Pacman package signing, DeveloperWiki:Package Signing Proposal for Pacman, and User:Allan/Package Signing

Flyspray: FS#5331

Development branch: mostly in mainline, or in patches on the pacman-dev ML.

Hooks

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: http://mailman.archlinux.org/pipermail/pacman-dev/2011-August/013961.html

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 here for a more detailed description.

Flyspray: (many - see above link)

Mailing List: http://mailman.archlinux.org/pipermail/pacman-dev/2010-November/012017.html, http://mailman.archlinux.org/pipermail/pacman-dev/2010-November/012018.html

Development branch: Not started

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: http://mailman.archlinux.org/pipermail/pacman-dev/2011-February/012466.html, http://mailman.archlinux.org/pipermail/pacman-dev/2011-February/012508.html

Pacsave numbered backups

Idea: If .pacsave already exists, move to .1, etc.

Flyspray: FS#24192

Mailing List: http://mailman.archlinux.org/pipermail/pacman-dev/2011-August/013981.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: http://mailman.archlinux.org/pipermail/pacman-dev/2011-July/013816.html

Future Release Plans

See flyspray roadmap