Info on the V.O.I.C.E RPM Packaging Engine
For V.O.I.C.E I, Ben Rietbroek, am working on
automating
RPM packaging.
The rationale for automating is:
- There is a lot of software out there we want to have packaged
- It would be a tedious task to manually write SPECFILES for each package
- Manually writing SPECFILES makes it hard to introduce conventions
- Manually writing SPECFILES makes it hard to do maintenance
-
Manually writing SPECFILES requires
low-level
rpmbuild knowledge
- Our community has limited resources, we need to make the best use of them
-
A lot of more reasons...
I will provide more insight of what I have been working on,
along with documentation, examples and what-not.
For now I will speak in images to give a first impression.
Layout of this page:
- The first two pictures relate to the MDE4OS2 Engine
- The next two pictures represent RPM Repositories with Packages and their Versions
- The last image shows a menu-driven interface to MDE4OS2
MDE4OS2 looks like this:
Some older information can be found here:
GnuHerd
AntHive
OHM
A builder takes input from Models and produces Results:
Here you see a model constructed from the Martin Examples:
Here you see a (partial) model of the upcoming V.O.I.C.E RPM Repositories:
Here you see a File-Commander Action-Menu:
=== That's all for today folks ! ===