<metapackage xmlns:os="http://opensuse.org/Standards/One_Click_Install" xmlns="http://opensuse.org/Standards/One_Click_Install">
  <group distversion="openSUSE Tumbleweed">
    <repositories>
      <repository recommended="true">
        <name>home:macknife</name>
        <summary></summary>
        <description></description>
        <url>https://download.opensuse.org/repositories/home:/macknife/openSUSE_Tumbleweed/</url>
      </repository>
      <repository recommended="true">
        <name>openSUSE:Factory</name>
        <summary>The next openSUSE distribution</summary>
        <description>openSUSE Tumbleweed: The Bleeding Edge, Perfected.
Tumbleweed is the ultimate rolling release distribution, providing the latest software as it’s released, built upon a foundation of world-class stability and testing.

* Always Current: Get the newest kernel, IDEs, desktops, and applications automatically.

* Powerfully Stable: Experience the velocity of a rolling release without sacrificing the reliability you depend on.

* Engineered for Professionals: The top choice for Developers, Power Users, and openSUSE Contributors who need the best tools for the job.

If you demand the latest stable software, your choice is Tumbleweed.

Staging dashboard is located at: https://build.opensuse.org/staging_workflows/openSUSE:Factory 

List of known devel projects: https://build.opensuse.org/package/view_file/openSUSE:Factory:Staging/dashboard/devel_projects

Have a look at http://en.opensuse.org/Portal:Factory for more details.</description>
        <url>https://download.opensuse.org/tumbleweed/repo/oss/</url>
      </repository>
      <repository recommended="true">
        <name>openSUSE:Tumbleweed</name>
        <summary>Tumbleweed</summary>
        <description>Tumbleweed is the openSUSE Rolling Release

This OBS Project represents the content of the currently published
snapshot. The newer repository for next publish can be found in openSUSE:Factory standard repository.
</description>
        <url>https://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/</url>
      </repository>
      <repository recommended="true">
        <name>openSUSE:Tumbleweed</name>
        <summary>Tumbleweed</summary>
        <description>Tumbleweed is the openSUSE Rolling Release

This OBS Project represents the content of the currently published
snapshot. The newer repository for next publish can be found in openSUSE:Factory standard repository.
</description>
        <url>https://download.opensuse.org/tumbleweed/repo/oss/</url>
      </repository>
      <repository recommended="false">
        <name>openSUSE:Factory</name>
        <summary>The next openSUSE distribution</summary>
        <description>openSUSE Tumbleweed: The Bleeding Edge, Perfected.
Tumbleweed is the ultimate rolling release distribution, providing the latest software as it’s released, built upon a foundation of world-class stability and testing.

* Always Current: Get the newest kernel, IDEs, desktops, and applications automatically.

* Powerfully Stable: Experience the velocity of a rolling release without sacrificing the reliability you depend on.

* Engineered for Professionals: The top choice for Developers, Power Users, and openSUSE Contributors who need the best tools for the job.

If you demand the latest stable software, your choice is Tumbleweed.

Staging dashboard is located at: https://build.opensuse.org/staging_workflows/openSUSE:Factory 

List of known devel projects: https://build.opensuse.org/package/view_file/openSUSE:Factory:Staging/dashboard/devel_projects

Have a look at http://en.opensuse.org/Portal:Factory for more details.</description>
        <url>https://download.opensuse.org/repositories/openSUSE:/Factory/ports/</url>
      </repository>
    </repositories>
    <software>
      <item>
        <name>dab-cmdline</name>
        <summary>Misc DAB commandline programs</summary>
        <description>- example 1 is the example where the main program is linked to
  a precompiled shared library,
  i.e. the DAB library should be pre-installed

- example 2 has the same functionality as example 1, the sources
      of the library are &quot;compiled-in&quot;, however.

- example 3 has the same functionality as example 2, and here
  the library sources are &quot;compiled in&quot; as well. However, the
  PCM samples are being sent out to stdout.
  One might use one of the available programs to make the sound
  audible
  dab-example-3 .... | aplay -r 48000 -f S16_LE -t raw -c 2

- example 4 has the sample functionality as examples 2 and 3, and
  here the library sources are &quot;compiled in&quot; as well. However,
  no sound decoding takes place. The MP2 frames (in case of DAB)
  and the AAC frames (in case of DAB+) are just emitted
  into a file or to stdout. A flag &quot;-f XXXX&quot; to the command
  line of this example, if specified, output is written to
  the specified file, otherwise to stdout.
  The output can be processed by e.g. VLC.
  (Note that the AAC frames have 960 rather than 1024 samples,
   not all audio programs are capable of handling these).

- example 5 is a small experimental extension to example 2,
  It contains a simple &quot;keyboard listener&quot;, that will react
  on entering a stroke on the return key. It will cause the
  &quot;next&quot; (audio) service to be selected.
  In example 5 there is support for tdc packet handling,
  and - thanks to stefan Juhl - support for FEC protected packets.

- example 6 is an experimental version where stdin is
  used as input device (and the command line parameters are
  adapted to that)

- the python example seems to work, the cmake file now expects
  python3.9 (it should work with other versions as well, adapt the
  CMakeLists.tct file)

- the scanner example is what the name suggests, it scans the band
  and shows the content of the channels that carry (detectable)
  DAB data.</description>
      </item>
    </software>
  </group>
</metapackage>
