On Friday 28 September 2007 03:23, Bernard Li wrote: > I suggest creating a separate repo for noarch.
No, not a "noarch" repository. It must be a "common-rpms" repository. Noarch packages can be distro dependent, as you know. Actually Jean and I talked about this at the end of August in Rennes and Jean wanted to change the upload script and repository directory structure. As long as that doesn't happen, I'd actually recommend using the old way of checking in freshly built packages into the normal trunk packages/distro/ directories. This way "make dist" will build you the tarballs and all and you can play with things. And RPMs are sorted, still. > BTW, are there any resolution to the i386 vs i686 issue? If people would use the scripts/build_oscar_rpms script, this wouldn't be an issue, as that automatically builds i686 rpms. > Also, currently OSCAR uses yume, which uses its own auto-generated > yum.conf during run time, so it will not even look at the .repo files > in /etc/yum.repos.d. 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. I recommend using the .url files for adding the gforge repository for now. This is simple and an affordable effort. 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
