-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'd say that shelling out for the RPM commands is not the way to go. That way lies pain and madness. We do that for our installer. Just simple stuff -- trying to parse the result of rpm -U <rpmname> -- results in information being returned in at least three different formats -- there are RPM names, there are suggested resolutions, and there are random file names that you have to map to an RPM manually. I'm sure that other rpm commands have their own oddities. yum and YaST both already provide interfaces into rpm functionality -- why don't you build on top of the libraries they use. I'd venture a guess that they provide a saner view of what's going on. Joe Van Dyk wrote: > I've been asked to create a GUI (runnable on RHEL3) that would prompt > the user with some questions (maybe via a wizard-like set of dialogs) > and then would install the appropriate RPMs based on the user's > questions. > > Any suggestions on tools/languages for that? Would I want to talk > directly to RPM libraries or would just running shell rpm commands > (and capturing the output) be probably all I need? > > Initially, I'm thinking that Python/pygtk would do, combined with > shell commands for the RPM installation. Sound reasonable? > > Thanks, > Joe > > _______________________________________________ > Rpm-list mailing list > Rpm-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/rpm-list - -- Marcin Krzysztof Porwit mporwit@xxxxxxxxxxxx #include <stddisclaimer.h> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFD89Bk4OZU6cX5VBERAoOXAJ9e8HcvL+LyCkrcfwT3WhH8PJxgsQCeNEQ4 2g/3IaxBdmjfbmuAAZTWicM= =+0+4 -----END PGP SIGNATURE----- _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
