John Hawk wrote: > A new toy for one and all to try IpsPkgTool Version 0.1 > > Image: http://home.comcast.net/~hawk.john/IpsPkgTool.jpg > Tar: http://home.comcast.net/~hawk.john/IpsPkgTool-V0.1.tar.bz2 > > Let me know what you think. Not responsible for spelling errors my mind was > out to the laundry. Please check my poor spelling.
John, I gave a try to your "toy" it's very nice and it's great to see that people from community *you* are getting involved in the IPS development. I have few comments: - For all the pkg(1) actions you are invoking pkg(1) command and parsing the output. Your application is written in python and IPS is also written in python, so it is much better to just plug your GUI to the IPS functions, than parsing output. - Running this application as an normal user is generating error that I am not a root. As far as I know IPS allows users to install things in their home directory. - All the actions that are time consuming for example "Process Queue" is in the same thread as GUI, which cause hang of the GUI. - How do you want to resolve problem with the package dependencies? So if you are selecting one package and another is dependent on the selected one, what then happens? I am working on the similar application, but what I don't want is to make additional layer between pkg(1) and GUI, so I am simply planning to call IPS functions. If you would like to try it: http://blogs.sun.com/migi/entry/indiana_ips_and_imagine -- all the best Michal Pryc _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
