FS#9237 - Libalpm documentation

Attached to Project: Pacman
Opened by Ben Dibbens (ibendiben) - Thursday, 17 January 2008, 01:06 GMT
Last edited by morganamilo (morganamilo) - Tuesday, 05 October 2021, 20:05 GMT
Task Type Support Request
Category General
Status Closed
Assigned To Rémy Oudompheng (remyoudompheng)
Architecture All
Severity Very Low
Priority Normal
Reported Version 3.1.0
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Summary and Info: It'd be nice to have the libalpm-man-page finished
This task depends upon

Closed by  morganamilo (morganamilo)
Tuesday, 05 October 2021, 20:05 GMT
Reason for closing:  Implemented
Additional comments about closing:  10 years later we have docs.
Comment by Dan McGee (toofishes) - Thursday, 17 January 2008, 01:27 GMT
Some doxygen docs are available. Download the source tarball and configure with --enable-doxygen, or clone the GIT repo and do the same.

There is also this:
http://code.toofishes.net/pacman/doc/
Comment by Yaro Kasear (Yaro) - Sunday, 08 May 2011, 03:20 GMT
I'd love to see documentation for alpm to be taken far more seriously. alpm is not that easy to use, which makes it harder for someone to contribute to Arch by, say, patchign pacman or writing a graphical package manager (We all know Arch needs an actually decent one in the AUR. The current pickings are not very good.)
Comment by Rémy Oudompheng (remyoudompheng) - Sunday, 08 May 2011, 07:55 GMT
There is indeed work going in this direction. Doxygen-type documentations are used for many libraries and this is usually sufficient. I don't think anybody is interested in writing a tutorial about how to write a package manager: this is essentially equivalent to writing a package manager. I personally think example scripts in pyalpm are a good start point for a high-level overview of libalpm usage.

Any contributions and proposals are welcome.

Loading...