Hi, since the oscar call was interrupted, we should continue on the mailing list.
DongInn described in the call how the installation steps go in the old OSCAR: 1. prereqs get installed (these are not opkgs, normally) 2. ODA is fed with config.xml data 3. core opkgs installed 4. selector is used to edit the default package set 5. ... selected opkgs are configured 6. server opkgs are installed on the master In the new setup we don't have the information from config.xml available and the ODA packages info is empty. We are directly querying the repositories so we can use selector without ODA, more or less. But it is unclear what is the best way to initiate and describe steps 1. and 3. in the new setup. For the start I would propose to leave the prereqs installation as it is and expect the prereq packages to be in the repositories. Step 2 is skipped. The step 3 can actually be done using the same querying functions we use in the selector, i.e. the functions from OpkgDB.pm: build a hash with all packages, find out which packages are "core" (multiplexed into the group information) and install their opkg-*-server rpms. When we're done with the selector it should create the default package set records. I think this is easilly doable and follows the philosphy of removing packaging info from the database. All we need in the database is the default package set and the package status. Other things can be read on the fly. Regards, Erich ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
