diff options
Diffstat (limited to 'meta-ibm/meta-romulus/conf')
| -rw-r--r-- | meta-ibm/meta-romulus/conf/distro/openbmc-romulus.conf | 1 | ||||
| -rw-r--r-- | meta-ibm/meta-romulus/conf/local.conf.sample | 4 |
2 files changed, 2 insertions, 3 deletions
diff --git a/meta-ibm/meta-romulus/conf/distro/openbmc-romulus.conf b/meta-ibm/meta-romulus/conf/distro/openbmc-romulus.conf deleted file mode 100644 index 2570a9a19..000000000 --- a/meta-ibm/meta-romulus/conf/distro/openbmc-romulus.conf +++ /dev/null @@ -1 +0,0 @@ -require conf/distro/openbmc-openpower.conf diff --git a/meta-ibm/meta-romulus/conf/local.conf.sample b/meta-ibm/meta-romulus/conf/local.conf.sample index 83a3f9b22..ef13391bf 100644 --- a/meta-ibm/meta-romulus/conf/local.conf.sample +++ b/meta-ibm/meta-romulus/conf/local.conf.sample @@ -63,9 +63,9 @@ MACHINE ??= "romulus" # Ultimately when creating custom policy, people will likely end up subclassing # these defaults. # -DISTRO ?= "openbmc-romulus" +DISTRO ?= "openbmc-openpower" # As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream +# where many versions are set to the absolute latest code from the upstream # source control systems. This is just mentioned here as an example, its not # useful to most new users. # DISTRO ?= "poky-bleeding" |