Keeping spec templates in a separate repo + using these in rpmdev-newspec (via `fedpkg new`?)

Project Discussion
1

We were discussing packaging pain-points at Flock, and thought of rpmdev-newspec, which, while useful, does not use spec templates that are up to date with our packaging guidelines. We do, however, have empty specs in the various ecosystem guidelines. So, we wondered:

  • if we could collect the spec templates in a git repository (under the packaging organisation on the forge) so that users can pull them (and not have to copy/paste from the docs)
  • possibly use these to update the templates that rpmdev-newspec uses
  • possibly adding a fedpkg new command that wraps around rpmdev-newspec—simply to make the workflow use fedpkg.

I’ve opened this topic here because I couldnt see an appropriate repo on our forge.

There are two other docs related tickets that also require comments/discussion:

2

I’m fine with using a template directory for packaged templates, it’s been on my todo list for a while. rpmdevtools is not a Fedora project and I don’t intend to make it more obviously Fedora-ish, though.

3

Thanks—i could probably pull out the empty specs in the guidlines and chuck them into a repo while we’re still at flock.

Yeh, that’s what i was told was behind the rpmdev-bumpspec templates not matching fedora ones. We could just not use rpmdev-newspec perhaps, and implement fedpkg new that simply pulls/fetches templates from our template repo?

1 Like
4

I’ve extracted all the spec templates from the guidelines here:

5

That’s also valid, it’s not like rpmdev-newspec in particular is that complex…

1 Like
6

PR here: