Wine Documentation | ||
---|---|---|
<<< Previous | Next >>> |
This document attempts to establish guidelines for people making binary packages of Wine.
It expresses the basic principles that the Wine developers have agreed should be used when building Wine. It also attempts to highlight the areas where there are different approaches to packaging Wine, so that the packager can understand the different alternatives that have been considered and their rationales.
An installation from a Wine pacakage should:
Install quickly and simply.
The initial installation should require no user input. An rpm -i wine.rpm or apt get wine should suffice for initial installation.
Work quickly and simply
The user should be able to launch Solitaire within minutes of downloading the Wine package.
Comply with Filesystem Hierarchy Standard
A Wine installation should, as much as possible, comply with the FHS standard.
Preserve flexibility
None of the flexibility built into Wine should be hidden from the end user.
Come as preconfigured as possible, so the user does not need to change any configuration files.
Use only as much diskspace as needed per user.
Reduce support requirements.
A packaged version of Wine should be sufficiently easy to use and have quick and easy access to FAQs and documentation such that requests to the newsgroup and development group go down. Further, it should be easy for users to capture good bug reports.
<<< Previous | Home | Next >>> |
Terms used in this document | Up | Requirements |