So i assume we do not try to "synchronize" Debian packages and RPM for this kind of stuff. Because as i said before, i did do something like that for Debian few weeks ago and i do not use the same names and i am not sure to split packages for same way.
Selon Erich Focht <[EMAIL PROTECTED]>: > Bernard, > > I just made a spec file and changed the Makefile such that > > % make baserpms > > will build you three oscar-base rpms. > > The RPMs will be: > oscar-base > oscar-base-libs > oscar-base-scripts > > See: > https://svn.oscar.openclustergroup.org/trac/oscar/changeset/6241 > > The perl "provides" are generated automatically for the oscar-base-libs rpm. > > Please modify the opkgc to require oscar-base-scripts on the clients (only > on rpm based builds, please, we don't want to break debian). The > oscar-base-scripts package will require oscar-base-libs. > > oscar-base is requiring both -scripts and -libs, so there is no need for > any oscar-base-server, IMO. > > Additionally: oscar-base is requiring yum, createrepo and yume. So these need > to be in an accessible repository or pre-installed. > > Thanks, > best regards, > Erich > > > > > On Thursday 04 October 2007 13:11, Erich Focht wrote: > > Hi Bernard, > > > > > > On Wednesday 03 October 2007 03:29, Bernard Li wrote: > > > http://svn.oscar.openclustergroup.org/trac/oscar/changeset/6235 > > > > yes, the issue seems solved. Thanks! > > > > > opkgc needs to be rebuilt and all the opkg-<package> RPMs will also > > > need to be rebuilt and uploaded to gforge. > > > > As said, the gforge structure for RPM based stuff is wrong. Please upload > stuff > > to the packages/*/distro/<distro><version>-<arch> directory, such that one > > can test without hassles. > > > > > However, this only fixes the dependency issue partially as > > > opkg-<package>-client/server still do not require opkg-<package> -- I > > > think they should, right? > > > > No, you're wrong. opkg-<package> was formelry known as opkg-api. It > contains > > the API scripts for the master, the config.xml and configurator.html and > > nothing else. These packages need to be installed on the master before > > really starting the installation! > > > > I am not sure about the place where to install the opkg-api packages. The > > procedure we allways talked of was: > > - query the repository for all package names with name matching ^opkg- > > - eliminate from the list all packages of the form > ^opkg-.*-(client|server)- > > - install the rest or use this for builing a list for the selector. > > - if second choice: install the opkg- packages selected in the selector. > > > > At server install time: install the packages opkg-<selected>-server. > > > > Still: we need: > > oscar-base : all OSCAR without packages/ and without prereqs packages. > > oscar-base-client : makes no sense for me. but we need a dummy rpm > > oscar-base-server : same as above. > > > > > This requires more poking around with the opkgc code, unless Jean can fix > this. > > > > > > Also, another issue related to dependencies is that currently the opkg > > > meta packages have a dependency on 'oscar-base-server' -- I could only > > > guess that this is supposed to be the RPM generated from the > > > oscar-base tarball (which contains all the /opt/oscar stuff). This > > > RPM/spec currently does not exist -- do we plan to create this any > > > time soon? > > > > > > If not, then perhaps we should remove it from the RPM spec file > > > template for opkgc. > > > > Please comment out oscar-base-server and oscar-base-client for now. We need > > oscar-base as a start. If you intend to work on this: remember the stuff > now > > has to go to /var/lib/oscar, at least this is where opkgc is putting the > > package info. I don't like this, because it means we'll have to change a > lot > > of documentation. But well... > > > > 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 > ------------------------------------------------------------------------- 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
