Sounds intersting, thank you. Could you describe in short what the sync anyway does? So which functionalities does it include? We'd like sync just to have a (in example) current.db.tar.gz provided (by path or how ever) and let alpm sync it with the current package db. We have plans not to implement any download feature of alpm, so downloading files (in our opinion) definitely is no task of the library / binding, but of the client, and i'm currently not sure if that's possible at all. So rather, we will want to use alpm for the following features: - Package DB handling (basically update pacman db dirs with the lib, by already existing pdbs in the fs) - Adding packages (so pulling depends, installing and adding it to the cache, handling the packages how ever the installed / not installed works. Also there, packages exist in the fs, which should be possible by setting another package cache dir for alpm) - Removing packages (as i wrote reverse-depend calc and handling of the uninstall process). Thank you, Georg On 5/4/07, VMiklos <vmiklos@frugalware.org> wrote:
Na Fri, May 04, 2007 at 09:44:50AM +0200, Georg Grabler <ggrabler@gmail.com> pisal(a):
pmsyncpkg_t There i'm unsure what it is used for, and if i need it at all. I could not find any function which i definitely need to call where this structure is used for.
cmiiw, but when you get the list of packages currently in the transaction, you'll need it (ie. when you add a pkg to a sync transaction and you would like to see what deps it pulled in)
VMiklos
-- developer of Frugalware Linux - http://frugalware.org