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
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
|
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
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
Can we *please* take 5 more seconds and get the category and version right too when we file a bug? Thanks.
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>
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')