Let's say I would like to create a module from postfix.
the output format postfix.yaml file looks like:
data: api: rpms: [postfix] components: rpms: postfix: {buildorder: 10, rationale: Package in api} tinycdb: {rationale: Build dependency.} dependencies: buildrequires: {base-runtime: f26, mariadb: f26, perl: f26, postgresql: f26, shared-userspace: f26} requires: {base-runtime: f26, shared-userspace: f26} description: Postfix is a Mail Transport Agent (MTA). filter: rpms: [tinycdb] license: content: [IBM and GPLv2+] module: [MIT] summary: Postfix Mail Transport Agent
Unfortunately based on postfix.spec, postfix SRPM provides these binary packages: - postfix-cdb - postfix-ldap - postfix-mysql - postfix-pcre - postfix-pgsql - postfix-sqlite
These package should be mentioned in api.rpms, I guess. Thanks for your comments.
but if you don't want to make all subpackages as an API?
You can specify API packages as the input e.g.:
./modulemd rpm2module postfix-cdb postfix-ldap postfix-mysql postfix-pcre
But this way name, description,.. etc. won't be filled automatically.
I very much agree with this issue. It would be awesome if the tool provided list of binary packages in the api section.
api
You can (and should) move them manually.
Login to comment on this ticket.