|
Karanbir Singh |
833109 |
add mock config files per package here;
|
|
Karanbir Singh |
833109 |
they can be either
|
|
Karanbir Singh |
833109 |
- <package name>-<version>-<releaese>.ARCH.conf
|
|
Karanbir Singh |
833109 |
- <package-name>-<version>.ARCH.conf
|
|
Karanbir Singh |
833109 |
- <package>.ARCH.conf
|
|
Karanbir Singh |
833109 |
|
|
Karanbir Singh |
833109 |
If the builder does not find a match in this dir, it will
|
|
Karanbir Singh |
833109 |
use the conf file from one dir up ( and should be good
|
|
Karanbir Singh |
833109 |
for most builds )
|
|
Karanbir Singh |
833109 |
|
|
Karanbir Singh |
833109 |
ARCH needs to be either i386 / x86_64 or noarch. In most cases
|
|
Karanbir Singh |
833109 |
we will want to use the default mock configs from one dir up
|
|
Karanbir Singh |
833109 |
and adapt those.
|
|
Karanbir Singh |
833109 |
|
|
Karanbir Singh |
833109 |
In almost every case, we want the noarch.conf to be symlinked
|
|
Karanbir Singh |
833109 |
to the x86_64 config file.
|
|
Karanbir Singh |
833109 |
|
|
Karanbir Singh |
833109 |
note: if doing custom mock configs for the kernel, its always
|
|
Karanbir Singh |
833109 |
going to need a noarch.cfg as well
|