Difference between revisions of "DeveloperWiki:Pacman Roadmap"

From ArchWiki
Jump to: navigation, search
m
Line 8: Line 8:
 
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.
 
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.0.X===
+
===Pacman 4.0===
  
 
Definitely included:
 
Definitely included:
Line 16: Line 16:
 
* libprovides/libdepends
 
* libprovides/libdepends
  
Maybes:
+
===Pacman 4.1===
 +
 
 +
Queued:
  
 
* Improved optdepend handling
 
* Improved optdepend handling
* Color output
+
* Pacsave non-overwriting file renames
* Parallel operations (mainly integrity checking and package loading)
+
  
Probably not:
+
Maybes:
  
 +
* Color output
 +
* Parallel operations (mainly integrity checking and package loading)
 
* Package/Transaction/File Hooks
 
* Package/Transaction/File Hooks
  
Line 74: Line 77:
 
===Parallel operations===
 
===Parallel operations===
  
'''Idea:''' Some things libalpm does are embarrassingly parallel, make it happen.
+
'''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 don't do parallel stuff on our own- namely DB loading stuff needs to be protected.
  
 
'''Flyspray:''' (None)
 
'''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
 
'''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:''' [https://bugs.archlinux.org/task/24192 FS#24192]
 +
 +
'''Mailing List:''' http://mailman.archlinux.org/pipermail/pacman-dev/2011-August/013981.html
  
 
==Future Release Plans==
 
==Future Release Plans==
  
 
See [http://bugs.archlinux.org/roadmap/proj3 flyspray roadmap]
 
See [http://bugs.archlinux.org/roadmap/proj3 flyspray roadmap]

Revision as of 14:12, 10 August 2011

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

Definitely included:

  • cURL as download library
  • Package Signing
  • libprovides/libdepends

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 Package Signing Proposal for Pacman.

Wiki: Pacman package signing, 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 don't 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

Future Release Plans

See flyspray roadmap