Hi Andrew, We don't actually create a clamav.spec file for building the RPM, or the equivalent for the DEB package. These packages are created by CMake's CPack tool.
The only special settings we add for supporting building RPM's and DEB's is this: https://github.com/Cisco-Talos/clamav/blob/main/CMakeLists.txt#L418-L437 At build time, we also set -D CPACK_DEBIAN_PACKAGE_RELEASE=1 , or -D CPACK_RPM_PACKAGE_RELEASE=1 and then after the build we run cpack -G DEB or cpack -G RPM and CPack does everything. Regards, Micah Micah Snyder ClamAV Development Talos Cisco Systems, Inc. ________________________________ From: clamav-users <[email protected]> on behalf of Andrew C Aitchison via clamav-users <[email protected]> Sent: Friday, October 28, 2022 11:45 AM To: [email protected] <[email protected]> Cc: Andrew C Aitchison <[email protected]> Subject: Re: [clamav-users] ClamAV 1.0.0 release candidate now available On Tue, 25 Oct 2022, Micah Snyder (micasnyd) via clamav-users wrote: > Read this announcement online at > https://blog.clamav.net/2022/10/clamav-100-release-candidate-now.html > > We are excited to announce the ClamAV 1.0.0 release candidate! > > You may find the source code and installers for this release on: > > * the clamav.net/downloads<https://www.clamav.net/downloads>, or > * the ClamAV GitHub release > page<https://github.com/Cisco-Talos/clamav/releases/tag/clamav-1.0.0-rc> > > Note: If you are looking for the source code on > clamav.net/downloads<https://www.clamav.net/downloads> - there is an > issue preventing the "Source" section from showing for release > candidates. Until we fix this issue, you find it under the "Linux" > section. > > Tip: If you are downloading the source from the GitHub release page, > the package labeled "clamav-1.0.0-rc.tar.gz" does not require an > internet connection to build. All dependencies are included in this > package. But if you download the ZIP or TAR.GZ generated by GitHub, > located at the very bottom, then an internet connection will be > required during the build to download additional Rust dependencies. It would be great if you could put the source debian/ directory and the clamav.spec file (for rpm builds) up with the source tarball. Tradition would say make the debian dir available as eg: clamav-1.0.0-rc-1.debian.tar.gz If you put clamav.spec at the top level (I think that means clamav-1.0.0-rc/clamav.spec ) then we can build the rpm straight from the tarball, with rpmbuild --ta clamav-1.0.0-rc.tar.gz This worked for RedHat 6, I don't have a current RedHat system to confirm. I know that you have mussels, but switching to CMake and adding Rust seems like enough for an OS packager trying to upgrade from one LTS to the next (0.103 to 1.0). Thanks, -- Andrew C. Aitchison Kendal, UK [email protected] _______________________________________________ Manage your clamav-users mailing list subscription / unsubscribe: https://lists.clamav.net/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/Cisco-Talos/clamav-documentation https://docs.clamav.net/#mailing-lists-and-chat
_______________________________________________ Manage your clamav-users mailing list subscription / unsubscribe: https://lists.clamav.net/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/Cisco-Talos/clamav-documentation https://docs.clamav.net/#mailing-lists-and-chat
