Without violating their proprietary license. Rpmbuild -ba ~/rpmbuild/SPECS/oracle-server.specĪnd users will end up with binary rpm packages, which they can install. The archive can be another file on the disk, a magnetic tape, or a pipe. Archives are files which contain a collection of other files plus information about them, such as their file name, owner, timestamps, and access permissions. Then they have to download those archives (in this case from ) and place them in ~/rpmbuild/SOURCES. GNU cpio copies files into or out of a cpio or tar archive. Now you have to instruct your users to do: You can freely distribute the resulting nosrc.rpm file. Positive side effects is that resulting file is much smaller. Resulting source package will include your scriptlets, patches, but will not include those archives. cpio copies files into or out of a cpio or tar archive, which is a file that contains other files plus information about them, such as their pathname, owner, timestamps, and access permissions. Today I wanted to transfer all my Oracle RDBMS installation files to remote Linux box. This package also includes mt, a tape drive control program.

This will create file oracle-server-10.2.0.4-78.el7. This is GNU cpio, a program to manage archives of files. The solution is to alter your spec file like: But that would contains those archives, which you are not allowed to redistribute. Which would create oracle-server-10.2.0. The oracle-server.spec file may look like this: Summary: Oracle 10g Database Server Enterprise Edition But how can I create and distribute proprietary software without violating license? The answer is ' nosrc.rpm'.įor example - let assume that you want to distribute Oracle Database Server with your custom settings and patches. I like to distribute software as RPM package because it allows me to put together patches, post-install scripts and configuration files.

Sometimes you have to deal with proprietary code.

10201 Database Linux X86 64.Cpio.Gz