Hello,

On Friday 28 September 2007 10:00, Jean Parpaillon wrote:
> Le 28.09.2007 03:42, DongInn Kim a écrit :
> > I have a little noise about common-rpms on gforge repository.
> >
> > Do we expect to upload all the common rpms to distro specific noarch 
> > directory on the gforge repo. As you all know, the common-rpms works for 
> > all the distros that OSCAR supports and we did not have to make a distro 
> > specific common-rpms tarball(e.g, 
> > http://oscar.openclustergroup.org/filebrowser/49/trunk). I think that it 
> > would be great if gforge can take care of common-rpms thing too like the 
> > current oscar nightly tarball.
> >   
> I'm thinking about this writing the new repository manager (which can be
> found on svn://svn.oscar......org/svn/pkgsrc/tools.repositories/).
> The way I plan to do it is:
> - a .src.rpm package is uploaded
> - rpms are built on each distro/arch
> - if rpm name contains one of mdv, fc, rhel in its name one built, it
> goes to distro specific repos. If not, it goes to common-rpms.
> 
> What do you think of it ?

I think two things:
1) If we start doing this, it implies rebuilding and rewriting most of the specs
again. This means very concretely: no chance for a release anytime soon. The
big changes introduced by the opkgc and the repository should finally stabilize
before even thinking of going new ways.

2) There is a script set for building RPMs automatically and putting them into
the right place. It is called scripts/build_oscar_rpms. It works with the
SRPMS/build.cfg file as input and is able to do the right thing in a trunk
checkout. It installs prerequisites and removes them after build, also it knows
about common rpms and the normal ones, as well as allows for additional
build options. The regular way to build is: check out trunk, make sure yume is
installed and working and has a distro repository somewhere. Then:
      cd $OSCAR_HOME/scripts
      ./build_oscar_rpms <opkg_name>
Stuff goes to distr/common-rpms and distro/... according to build.cfg.


The switch to the central repository is nice and fine, when it starts working,
but for now it looks quite difficult to maintain versions of stuff. Remember:
on RPM based distros we have a whole lot more packages than on debian, so we
build much more stuff.

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

Reply via email to