I like the idea but i have a naive question: why is it yume based? It seems to me that it should be great to have a generic smart-packman-opkg. Smart-packman-opkg gets the list of packages and then call "smart-packman" (which will call yume or apt). Doing that, with the same code, we can use yume for RPM based distros as well as Deb based distro, we just have to port the smart-packman interface on apt.
With the current implementation, what is the interface to plug apt? Write apt-opkg? duplicating 80% of the yume-opkg code? To summarize why do not we try to have a higher level of abstraction? Does it make sense? Thanks, Le Mercredi 26 Avril 2006 11:46, Erich Focht a écrit : > Hi, > > as promised yesterday, "it will work tomorrow". Luckilly, this was indeed > today ;-) > > Here's the updated version of yume-opkg which works with the OSCAR5 > database. Actually it has a bit too much functionality, but that can be > stripped off. > > Usage examples: > > # list selected opkgs (Default group) > yume-opkg --list > > # list rpms belonging to ganglia opkg > yume-opkg --list --rpms ganglia > > # list rpms belonging to ganglia on the oscar_client group nodes > yume-opkg --list --rpms --group oscar_client ganglia > > If you replace --list by --install, it will attmpt to install the packages. > If you add --image=PATH_TO_IMAGE it will apply all actions to the chroot > image path. > > In the future, when we get direct access to the database from the clients > and OS_Detect working on the clients, yume-opkg will simply work on the > clients. > > > Best regards, > Erich > > > USAGE: > ./yume-opkg --distro DISTRO --distrover DISTRO_VERSION [--group GROUP] \ > [--arch ARCH] [--list|--install|--update|--remove] [--all] \ > [--image IMAGE_DIR] [--repo REPO_URL ...] [--yes] [--rpms] \ > [--test] [--verbose|-v ...] [opkg1 [opkg2 ...]] > > Query/install/update/remove OSCAR packages, corresponding RPMs, > which belong to a particular node group (e.g. oscar_server or > oscar_client, use no group for common packages). > Options: > --distro D : distribution name as used in config.xml > --distrover V : distribution version as used in config.xml > Example: --distro redhat --distrover el4 > --group G : node group as used in the OSCAR database, for > example: oscar_server, oscar_clients > --arch A : architecture, overriding local machine architecture > --all : select all opkgs in the default set > --rpms : list rpms belonging to the selected opkgs > > --list : list opkgs or rpms > --install : install rpms by using yum(e) > --update : update rpms with yum(e) > --remove : remove rpms with yum(e) > > --repo R : specify package repository for yum(e). > --test : just show what would be done, don't do it. > --yes|-y : pass "yes" to yum if it requires input. > --verbose|-v : increase verbosity of output. -- Geoffroy R. Vallee, Ph.D. Oak Ridge National Laboratory Voice: 865-574-3152 P.O. Box 2008, Bldg. 5600 Fax: 865-576-5491 Oak Ridge, TN 37831 -- Geoffroy ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642 _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
