Changes between Version 17 and Version 18 of RpmHowToPackagers
- Timestamp:
- Sep 9, 2011, 4:09:02 PM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
RpmHowToPackagers
v17 v18 128 128 }}} 129 129 130 === Repacking old software===131 When you create RPM packages for software that you don't build from sources (like some old OS/2 programs that areonly available in the binary form), you need to follow a special procedure in order to preserve the sizes and timestamps of the original files (which may be important for their identification in case if someone needs that).130 === Repacking binary software archives === 131 When you create RPM packages for software that you don't build from sources (like old OS/2 programs or any other software that is only available in the binary form), you need to follow a special procedure in order to preserve the sizes and timestamps of the original files (which may be important for their identification in case if someone needs that). 132 132 133 133 1. Add the following to the .spec file (somewhere before the %install section): … … 138 138 2. Use 139 139 {{{ 140 cp - Rdp <src> <dst>140 cp -dp <src> <dst> 141 141 }}} 142 in the %install section when you copy files from BUILD to BUILDROOT for getting packed by rpmbuild; the naked cp command will kill the original timestamp (the <dst> file will get the current time). 142 in the %install section when you copy files from BUILD to BUILDROOT for getting packed by rpmbuild; the naked cp command will kill the original timestamp (the <dst> file will get the current time). The -p flag causes cp to preserve timestamps and the -d flag preserves symlinks (just in case a file you copy is a LIBC symlink). Another cp flag you may find useful is -R which causes it to copy directories recursively. 143 143 144 144 === CONFIG.SYS changes ===