ok. thanks. what needs to contain in binary package installation of debian/RPM is the content under the install folder of the corresponding package, am I right ? If it’s right, does it work with the following process for RPM creation for quick prototype/verification? as follow:
- For RPM
%buildpart: invoke thecolconto build a package normally as the way to build with source code - For RPM
%installand%filespart: manually add the content of the corresponding package underneath theinstallfolder of the workspace (that’s to say you have already know the details of theinstallfolder with the way of source building) - finally, rpmbuild with the above rules of spec file to create the RPM package
I know that it’s not feasible to manually create spec and RPM for many package in this way, and it also requires a great deal of effort to maintain, just try to verify one project before further code development. 