You are not logged in.
Pages: 1
Hey, i've been working on a package manager (GUI actually) for arch but i have a problem i need the documantation of the library to keep working, i don't know if someone know where i can find it. I've tried man libalpm and is not what i've been looking for. If anyone could help me find something that could help me developing the package manager would be great
by the way the project is in GTK and i've been writing the code in C.
Offline
IMO best way would be to look at pacman source.
You can try this doxygen docs , but i think its nowhere near complete http://code.toofishes.net/pacman/doc/index.html
Offline
Ok thank you I think that will help me;)
Offline
IMO best way would be to look at pacman source.
You can try this doxygen docs , but i think its nowhere near complete http://code.toofishes.net/pacman/doc/index.html
Doxygen is the best source at the moment. There are quite a few things that haven't been documented yet, so you'd have to look at the source code for that. If you do run into anything that lacks documentation, please do point it out. I think I'll be working on improving the documentation soon.
Offline
I think I'll be working on improving the documentation soon.
That would be awesome! Even though I do actually work on libalpm code, I still have no idea what most things do (and have to grep through pacman to find out). That is why all my changes to the pacman code so far have been really small.
Offline
> Hey, i've been working on a package manager (GUI actually) for arch [...]
You might have a look at these for some inspiration:
http://bbs.archlinux.org/viewtopic.php?id=51680
http://wiki.archlinux.org/index.php/Pac … _Frontends
http://chakra-project.org/tools-shaman.html
1000
Offline
Am I correct in thinking that libalpm is just the code behind pacman, i.e. desc and depends file parsers, database updaters, dependency resolvers, etc?
My Arch Linux Stuff • Forum Etiquette • Community Ethos - Arch is not for everyone
Offline
Am I correct in thinking that libalpm is just the code behind pacman, i.e. desc and depends file parsers, database updaters, dependency resolvers, etc?
Yes. pacman is now just a frontend to libalpm.
Offline
@Xyne
<hint> Currently python bindings exist for libalpm but not perl . If it was there it would be far easier to do more awesome stuff </hint>
Offline
@Xyne
<hint> Currently python bindings exist for libalpm but not perl . If it was there it would be far easier to do more awesome stuff </hint>
Looking over the code for the python bindings (not sure if it's the same bindings) it seems it's no where near complete and has a terrible interface (ALPM is a class in itself, and that's all there is).
That would be awesome! Even though I do actually work on libalpm code, I still have no idea what most things do (and have to grep through pacman to find out).
Indeed. I've been trying to get familiar with just the interface for quite some time and I'm still confused by some things. It'll probably be a while still before I'm actually familiar enough to write the documentation. There seem to be a few "pacman-isms" which confuse me even more. Maybe the interface will be improved as a result too .
Offline
Pages: 1