RPM Development Tools

Edit Package rpmdevtools
https://pagure.io/rpmdevtools

This package contains scripts and (X)Emacs support files to aid in
development of RPM packages.
rpmdev-setuptree Create RPM build tree within user's home directory
rpmdev-diff Diff contents of two archives
rpmdev-newspec Creates new .spec from template
rpmdev-rmdevelrpms Find (and optionally remove) "development" RPMs
rpmdev-checksig Check package signatures using alternate RPM keyring
rpminfo Print information about executables and libraries
rpmdev-md5/sha* Display checksums of all files in an archive file
rpmdev-vercmp RPM version comparison checker
spectool Expand and download sources and patches in specfiles
rpmdev-wipetree Erase all files within dirs created by rpmdev-setuptree
rpmdev-extract Extract various archives, "tar xvf" style
rpmdev-bumpspec Bump revision in specfile
...and many more.

Refresh
Refresh
Source Files (show unmerged sources)
Filename Size Changed
dont-drop-Groups.patch 0000000989 989 Bytes
limit_newversion_re.sub_to_a_single_replacement.patch 0000001424 1.39 KB
python3-shebang.patch 0000001729 1.69 KB
rmdevelrpms_fix_filename_search.patch 0000000773 773 Bytes
rmdevelrpms_use_more_raw_strings.patch 0000001208 1.18 KB
rpmdevtools-8.10.tar.xz 0000094976 92.8 KB
rpmdevtools-rpmlintrc 0000000114 114 Bytes
rpmdevtools.changes 0000011570 11.3 KB
rpmdevtools.spec 0000004598 4.49 KB
skeleton 0000010645 10.4 KB
suse-specfile.patch 0000024758 24.2 KB
Latest Revision
buildservice-autocommit accepted request 827857 from Luigi Baldoni's avatar Luigi Baldoni (alois) (revision 30)
baserev update by copy to link target
Comments 5

Martin von Reichenberg's avatar

rpmdevtools version 9.6 available for some time . . . . .
https://releases.pagure.org/rpmdevtools/?C=M;O=D
https://releases.pagure.org/rpmdevtools/rpmdevtools-9.6.tar.xz


Luciano Santos's avatar

Yes, it is, Martin. And unfortunately it may never see the light of day in openSUSE.

Why? Because:

  1. It requires additional packages;
  2. It changes to the RPM package; and
  3. It introduces a build cycle.

1 is not much of a problem; 2 should be reviewed carefully to see if it's worth the effort; and 3 the Factory maintainers won't be happy about it.

Someone (maybe my future self) could try to patch it, somehow. However, it's too much fun to have, and I'm not willing to play with that, at least for now. I have other things with higher priority to get done first.


Martin von Reichenberg's avatar

But why is it ignored even by "RPM experts" when the RPM package development on SUSE relies heavily on rpmdevtools ?_?

Isn't it strange, a pity or even a shame ?_?


Luciano Santos's avatar

Well, I can't speak for SUSE packagers with authority. But you might be surprised that openSUSE package development can ignore rpmdevtools's existence completely.

Is there any helpful tool that we can incorporate to our workflows? Sure it does. Is any of them essential? I don't think so. Taking myself as an example, I only crossed paths with rpmdevtools after a long time working with openSUSE packages.

We have our whole tool box around OBS. So, yeah "RPM experts" have been ignoring it around here, and must probably will keep doing so.


Luciano Santos's avatar

With the upcoming RPM 4.18 release, perhaps things will look brighter. We'll see.

openSUSE Build Service is sponsored by