Difference between revisions of "Category:Packaging Policies"

Latest revision as of 10:46, 1 May 2014

This category contains policies that should be followed when packaging software for ROSA Linux.

Some policies apply for a wide range of packages (e.g., if you package an application which should be integrated into desktop environment, you should read XDG menu system policy), while the others are specific to particular software area (e.g., Python policy describes packaging of Python extensions).

System-wide policies

• Charset policy - some aspects concerning charset to be used in spec file
• Initscripts policy - how to package initscripts if your application needs them
• Libraries policy - how to package software providing libraries intended to be used by other applications
• Licensing policy - how software licenses should be managed
• Localization policy - how to package localization files
• SSL certificates policy - how to deal with SSL certificates if your application uses them
• XDG menu system policy - how to add XDG menu support to a packaged application

Subsystem-specific policies

• DKMS policy - packaging kernel modules as DKMS packages
• Fonts policy - packaging fonts
• KDE SC 4 packaging policies - packaging KDE 4 components
• Node.js policy - packaging Node.js modules
• Perl policy - packaging Perl modules
• Python policy - packaging Python extensions
• Ruby policy - packaging Ruby extensions
• Web applications policy - packaging applications which should be accessed using a web server