Hi, I am not sure that OPKGC and PackageInUn address the same problems: PackageInUn makes the interface between the database and the underlying binary package management system (yum, apt, or whatever else). So i think PackageInUn will be simplified when we will use binary packages, but i do not think OPKGC will "replace" PackageInUn.
Unfortunately I do not have the time right now to give more details about that, i am kind of overbooked. But the PackageInUn specification (which is not implemented) is online, feel free to have a look and give comments: https://svn.oscar.openclustergroup.org/trac/oscar/wiki/PackageInUn Moreover, if i am not clear, let me know i will try to answer in few days. Last point: since the PackageInUn code is currently broken, i think this is fine if we remove it from the GUI. My 2 cents, Le mardi 29 mai 2007 14:58, Kim, DongInn a écrit : > Hi, > > I am wondering if we are dropping the User Friendly interface(GUI) for > implementing "Package Install/Uninstall" (in short, PackageInUn) feature > at oscar_wizard when opkgc is fully imported to the oscar installation. > http://oscar.openclustergroup.org/comp_opkgc > (FYI, we are not losing the feature of installing/uninstalling packages > and I believe that opkgc can take care of this.) > > PackageInUn was implemented in oscar_wizard (install/manage mode) until > oscar 4.2 and it has been one of OSCAR main functionalities that I like > to use to maintain my OSCAR cluster. > > But looks like that we have not planned to make any GUI to implement the > previous PackageInUn stuff on OSCAR 5.1 yet. > > The features that the previous PackageInUn can do are > 1. Add new package(s) to the existing cluster > 2. Remove/Uninstall some packages from the existing cluster > 3. Update oscarimage according to the addition or removal of the packages. > 4. Update the "Node_Package_Status" table in oda. > 5. It was integrated with "Selector" (i.e., "Select OSCAR Packages..." > menu at oscar_wizard (manage mode)) > 6. GUI > > I do not really care about the GUI as long as opkgc (the new OSCAR > package management tool) can handle the obvious and inevitable issues > above but not all possibly. > > In addition, if we can not do this via opkgc until OSCAR5.1 or if it is > not worth to make the similar PackageInUn via opkgc, I think we need to > provide a full instruction/document of managing OSCAR packages in the > similar way that PackageInUn could have done it. > > What do you guys think about this? -- Geoffroy ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
