I created a script (I'll add it to CVS later) that writes proper mock
config files for all the different RPM Fusion builders. That should make
things a whole lot easier when it comes to creating configs for new
releases/builders or other adjustments to the config files. After that I
* reconfigured (see archives for reasons why) mock on
builder.wilsonet.com with the new config files and enabled the builder again
* updated the mock configs on the ppc builder to the new ones
* disabled the two other x86 builders to give builder.wilsonet.com some
more testing over the next few days
If there are any problems let me know via mail; it would be nice if you
guys could check the logs and results of your builds carefully.
If nothing shows up over the next two days I'll update mock and the mock
configs on the two other x86 builders as well.
Do we really want to install the foo2* packages by default? Isn't there
some kind of automatic printer driver download feature these days that
maybe can be used?
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion(a)cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
I don't remember reading a discussion about this. Is there anyone who
made some research about OSSv4? I saw some good reviews and some folks
in fedoraforum are asking about it.
Can it be considered for RPMFusion? Practically, it replaces ALSA, or
maybe it can be thought as an alternative.