AutoYAST - patterns

Hello :slight_smile:

I created my autoinst.xml, and I would like to ask if there is a possibility to install patterns with the –no-recommends switch (i.e. zypper in --no-recommends -t pattern x11)?
How should I enter it into autoinst.xml?

<patterns config:type="list">
      <pattern>apparmor</pattern>
      <pattern>apparmor_opt</pattern>
      <pattern>base</pattern>
      <pattern>enhanced_base</pattern>
      <pattern>enhanced_base_opt</pattern>
      <pattern>fonts</pattern>
      <pattern>fonts_opt</pattern>
      <pattern>laptop</pattern>
      <pattern>minimal_base</pattern>
      <pattern>sw_management</pattern>
      <pattern>yast2_basis</pattern>
      <pattern>x11</pattern>
      <pattern>gnome_basis</pattern>
    </patterns>

When I set

<install_recommended config:type="boolean">false</install_recommended>

YAST is installing only ~30 packages, without kernel, grub, etc…
Any idea? :frowning:


<software>
  <install_recommended config:type="boolean">false
  </install_recommended>
</software>

Should do the trick.

Really, it’s works :). It was my mistake, sorry :'(. Thank you very much Miuku;).
I have another question. It’s able to seperate patterns (i.e. pattern a,b with recommends, pattern c without recommends)?

Unfortunately no but you can manually look at the pattern and then add the packages to your

<packages> </packages>

list.

To see what packages a pattern recommends, you can use something like:

zypper info --recommends -t pattern lamp_server

Miuku, thank you very, very much for assistance :slight_smile:
I installed system without x11 and gnome_basis patterns. I don’t need i.e. Firerox (I use Google Chrome), VNC assigned to gnome_basis/x11 pattern. I’ve installled packages manually, using

zypper pattern-info pattern

and select only requred packages.
Finally all works fine :slight_smile:

Keep in mind that FF from the openSUSE repos supports the “One-Click Install” from the software search site, other browsers won’t (as a general rule even from the openSUSE repos).

As a workaround, you might be able to download the yml file and point YaST Software Manager at it manually, or open the file in a text editor and use the info to manually configure adding repositories and installing packages.

TSU