Whole document tree 6. Allways Provide RPM Packages of Your SoftwaresThis is extremelly important for many reasons:
But a good package is not only put together your files in a RPM. FHS must be followed, configuration and documentation files must be marked como tal, and pre- and post-install scripts must be robust, to not let them damage the system (remember that installation processes is done by root). Know well RPM because it can bring much power and facilities to you and your user. There are a lot of documentation available about RPM on the Internet:
6.1. Software Package ModularizationYou should give user the option to install only the part of your Software he wants. Imagine your Software has a client part and a server part, and both use files and libraries in common. You should break them in 3 RPMs. For instance, lets say the name of your product is MyDB, so you'll provide the packages:
and last 2 packages depends on the first. If the user is installing a client profile, he will use:
If he is installing a server profile:
This approach will help the user save disk space, and be aware of how your Software is organized. |