Guys, just want to make sure you don't put too much effort into the opkg requires/provides/excludes part. These relationships will become obsolete and won't need to live in the database when the opkg-to-rpms compiler is finished.
As discussed at the OSCAR conference, we're planning to compile meta-packages out of the opkg information such that when installing OSCAR only the native package manager of the distro (rpm, deb) will be in use. The transition to pure repository distribution was the first step towards this target. This will stop us from working on the replication of package manager functionality for opkgs and allow us to use the low level package managers dependencies, requires, exclusions, etc at no additional development and maintenance cost. I'll try putting some specs into the wiki soon. Ideally this will lead to a simplification of ODA, such that we can finally start feeding it with what is more relevant for clusters: node group information, node info (SIS->ODA), cluster configuration data. Regards, Erich All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
