![](https://seccdn.libravatar.org/avatar/5c786b1b80718534429c90c4126cd5ab.jpg?s=120&d=mm&r=g)
Jethro Cramp
It's been a while since I looked at it, but when you roll your own rpm don't you have to know every single file that is going to be installed and where it will be installed? How do you accompolish this?
Use a BuildRoot and then install accordingly. For instance for makefiles that support DESTDIR simply do 'make DESTDIR=$RPM_BUILD_ROOT' and everything gets installed in the BuildRoot. Now make sure there is no %clean in the specfile (remove it if present) and the build root directory will not get deleted. Now simply do a 'find /path/to/build_root' and you get a list of all directories and files the installation created. From that list it's easy to create a %files section. This also shows the advantage of using rpm over checkinstall: you install to a build root and *not* into the running system. Therefor you - don't have to be root to build the rpm - you don't overwrite installed software and thus have less chance to mess up your system. Philipp -- Philipp Thomas work: pthomas@suse.de private: philipp.thomas@t-link.de