There are lot of packages that can't be hosted on the Build Service.

The idea would be a tool where you can say:

emerge Foo

and it goes to the (preconfigured or default) project, checks out the .spec files (which may or may not have the tar.bz2), download the tarballs if needed, build the package locally. Install it, and put the result in a cache.

BUT.... more important than that... recursively do this to build the required dependencies that are missing from the system.

I am pretty sure this can be done using all the stack we are already using: OBS, osc, build, plus some extra magic and integration work.

May be it could also be designed using some recursive packaging, so a spec file that builds an rpm that contains the sources to build an rpm.

Looking for mad skills in:

rpmbuild rpm buildservice packaging

This project is part of:

Hack Week 11


  • almost 3 years ago: mbologna liked "emerge" for rpm/SUSE
  • over 5 years ago: rneuhauser liked "emerge" for rpm/SUSE
  • over 5 years ago: dsterba liked "emerge" for rpm/SUSE
  • over 5 years ago: oholecek liked "emerge" for rpm/SUSE
  • over 5 years ago: dmacvicar added keyword "packaging" to "emerge" for rpm/SUSE
  • Show History


    • sleep_walker
      over 5 years ago by sleep_walker | Reply

      Maybe some other name would be great not to collide with Gentoo's emerge.

      • oholecek
        over 5 years ago by oholecek | Reply

        What about being this as a part of zypper stack. Like zypper em(erge)

    • dmacvicar
      over 5 years ago by dmacvicar | Reply

      Yeah, the name was just an example :-) and the idea of a zypper subcommand is a good one too

    Similar Projects

    Properly package Quick Event orienteering management software by LPechacek

    It ain't rocket science, it ain't thrilling, it...