<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>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>
    </repositories>
    <software>
      <item>
        <name>perl-Sub-Exporter-Progressive</name>
        <summary>Only use Sub::Exporter if you need it</summary>
        <description>Sub::Exporter is an incredibly powerful module, but with that power comes
great responsibility, er- as well as some runtime penalties. This module is
a 'Sub::Exporter' wrapper that will let your users just use Exporter if all
they are doing is picking exports, but use 'Sub::Exporter' if your users
try to use 'Sub::Exporter''s more advanced features, like renaming exports,
if they try to use them.

Note that this module will export '@EXPORT', '@EXPORT_OK' and
'%EXPORT_TAGS' package variables for 'Exporter' to work. Additionally, if
your package uses advanced 'Sub::Exporter' features like currying, this
module will only ever use 'Sub::Exporter', so you might as well use it
directly.</description>
      </item>
    </software>
  </group>
</metapackage>
