Difference between revisions of "DeveloperWiki:Pacman Roadmap"

From ArchWiki
Jump to: navigation, search
(New Feature Ideas)
 
(47 intermediate revisions by 7 users not shown)
Line 1: Line 1:
[[Category:Pacman development (English)]]
+
[[Category:Pacman development]]
 
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.
 
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 [http://mailman.archlinux.org/pipermail/pacman-dev/ pacman-dev] mailing list.
+
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 [https://mailman.archlinux.org/pipermail/pacman-dev/ pacman-dev] mailing list.
  
 
==Potential Release Schedule==
 
==Potential Release Schedule==
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===
 
  
Definitely included:
+
===Pacman 5.1===
  
* cURL as download library
+
Applied:
* 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==
 
==New Feature Ideas==
  
===Package Signing===
+
===Package Signing - Polishing===
 
 
'''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:''' [https://bugs.archlinux.org/task/5331 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 [[User:Allan/Pacman_Hooks|here]] for a more detailed description.
 
  
'''Flyspray:''' [https://bugs.archlinux.org/task/2985 FS#2985]
+
'''Idea:''' Tidy up our current implementation of package signing.
  
'''Mailing List:'''
+
'''Flyspray:''' {{bug|28014}} {{bug|34741}}
* http://mailman.archlinux.org/pipermail/pacman-dev/2010-July/011441.html (first of set of four)
 
* http://mailman.archlinux.org/pipermail/pacman-dev/2011-January/012313.html
 
* http://mailman.archlinux.org/pipermail/pacman-dev/2011-January/012335.html
 
  
'''Development branch:'''
 
Not started
 
  
 
===Optdepend Handling===
 
===Optdepend Handling===
Line 60: Line 27:
 
'''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 [[User:Allan/Pacman_OptDepends|here]] for a more detailed description of what is currently being implemented.
 
'''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 [[User:Allan/Pacman_OptDepends|here]] for a more detailed description of what is currently being implemented.
  
'''Flyspray:''' [https://bugs.archlinux.org/task/12708 FS#12708] (and others)
+
'''Flyspray:''' {{bug|12708}} (and others)
  
'''Mailing List:''' http://mailman.archlinux.org/pipermail/pacman-dev/2011-August/013961.html
+
'''Mailing List:''' https://mailman.archlinux.org/pipermail/pacman-dev/2011-August/013961.html
  
 
'''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)
 
 
'''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===
 
===Parallel operations===
Line 81: Line 39:
 
'''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:''' 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:''' [https://bugs.archlinux.org/task/24192 FS#24192]
 
 
 
'''Mailing List:''' http://mailman.archlinux.org/pipermail/pacman-dev/2011-August/013981.html
 
  
 
===Iterator interface for databases===
 
===Iterator interface for databases===
 
'''Idea:''' Provide an iterator interface for databases, especially those with 'files' entries, to keep memory usage in check.
 
'''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
+
'''Mailing List:''' https://mailman.archlinux.org/pipermail/pacman-dev/2011-July/013816.html
  
 
==Future Release Plans==
 
==Future Release Plans==
  
See [http://bugs.archlinux.org/roadmap/proj3 flyspray roadmap]
+
See [https://bugs.archlinux.org/roadmap/proj3 flyspray roadmap]

Latest revision as of 03:40, 25 March 2016

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 5.1

Applied:


New Feature Ideas

Package Signing - Polishing

Idea: Tidy up our current implementation of package signing.

Flyspray: FS#28014 FS#34741


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