Hi Bernard, On Monday 01 October 2007 19:08, Bernard Li wrote: > On 10/1/07, Erich Focht <[EMAIL PROTECTED]> wrote: > > > No, not a "noarch" repository. It must be a "common-rpms" repository. > > Noarch packages can be distro dependent, as you know. > > Yes, I am aware of that, but presently there is no "common-rpms" but > there is "noarch", and it is incorrectly referenced in the .repo file. > That is what I wanted fixed.
I suppose that was done in analogy to debian, who holds all archs in one repository and clearly have a noarch subdir. I see no reason to again change the repository structure for RPM based distros. Confusion is big enough... > We can stick with the old way, as you suggested, but we need to > incorporate the opkg-* meta packages because OSCAR trunk currently > will not install, unless those packages are available. For some > distributions they are uploaded to gforge. I suppose we could also > build and check them into the SVN repository in each packages' > distro-specific RPMs directory. Initially I expected that in a first step we'd do it this way. Until stuff gets stable. Then I expected that maybe we upload only the opkg-* rpms to a central place. Oh well, I'm a friend of rather clean transition steps... We need urgently a plan to get trunk back running for all distros. > > The purpose of yume was actually to override the yum repository settings. > > The > > reason for that is the need to closely control the package versions > > installed > > on a cluster (and have the same versions on every node). Some of the people > > on this mailing list can certainly tell you about the nightmare of having > > master and clients installed with different update levels... yume helps you > > to keep this under control by ignoring the default yum repositories. > > Sure, that's fine -- you can still do this by describing OSCAR > repositories in .repo files in the /etc/yum.repos.d directoriy and > using the internal yum arguments --disablerepo, --enablerepo so > something like `yum --disablerepo=* --enablerepo=oscar_i386 > --enablerepo=oscar_noarch` etc. would allow you to control which > specific repositories to use. In the early days this didn't make sense, but now it does, more and more. Still, I'd consider this a minor issue compared to the rest of the trouble. Regards, Erich ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
