Pacman

Historical bug tracker for the Pacman package manager.

The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues

This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
Tasklist

FS#9146 - optdepends not documented

Attached to Project: Pacman
Opened by Pierre Schmitz (Pierre) - Thursday, 10 January 2008, 10:41 GMT
Last edited by Dan McGee (toofishes) - Friday, 11 January 2008, 05:17 GMT
Task Type Bug Report
Category Documentation
Status Closed
Assigned To Dan McGee (toofishes)
Architecture All
Severity Low
Priority Normal
Reported Version 3.1.0
Due in Version 3.1.1
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

There is no reference to optdepends in man PKGBUILD
This task depends upon

Closed by  Dan McGee (toofishes)
Friday, 11 January 2008, 05:17 GMT
Reason for closing:  Fixed
Additional comments about closing:  fixed in git
http://projects.archlinux.org/git/gitweb .cgi?p=pacman.git;a=commit;h=71ca587f2a4 7a9ed8f9497d4685989e00f968202
Comment by Roman Kyrylych (Romashka) - Thursday, 10 January 2008, 11:57 GMT
optdepends are not yet implemented, only preliminary support was added.
Comment by Dan McGee (toofishes) - Thursday, 10 January 2008, 13:53 GMT
  • Field changed: Status (Unconfirmed → Assigned)
  • Field changed: Category (General → Documentation)
  • Field changed: Reported Version (3.0.6 → 3.1.0)
  • Field changed: Due in Version (Undecided → 3.1.1)
  • Task assigned to Dan McGee (toofishes)
They are implemented as much as we are going to implement them for now, however. They can still be documented.

Can we *please* take 5 more seconds and get the category and version right too when we file a bug? Thanks.
Comment by Pierre Schmitz (Pierre) - Thursday, 10 January 2008, 16:54 GMT
Sorry for forgetting to mention the exact version.

Am I right in describing the current implementation as follows:
* We can add optdepends in a PKGBUILD and its information are stored in the package. No other checks are done.
* There is no impact when installing such a package
* You can see those dependencies when issuing pacman -Qi <package>
Comment by Aaron Griffin (phrakture) - Thursday, 10 January 2008, 18:55 GMT
I'm with Dan here. It's not fully implemented so no need to document it. Still, feel free to provide a patch if you want to escalate the matter.
Comment by Dan McGee (toofishes) - Thursday, 10 January 2008, 19:04 GMT
Err...I said we *should* document it. I reopened the bug after Roman closed it before I even had a chance to look at it.

I was planning on doing this before 3.1.1, unless someone else wants to provide a patch.

Pierre- exactly right on the description. They are in the following format as well:

optdepends=('sampledep1: for blah' 'sampledep2: install for foo functionality')

Loading...