Module Guidelines
(Difference between revisions)
m (→CONFLICTS: Both modules must have a CONFLICTS file) |
m (→CONFLICTS: Forgot the star) |
||
| Line 19: | Line 19: | ||
== CONFLICTS == | == CONFLICTS == | ||
| − | Remember to add a CONFLICTS to both modules that conflict with each other. | + | * Remember to add a CONFLICTS to both modules that conflict with each other. |
== CONFIGURE == | == CONFIGURE == | ||
Revision as of 15:59, 27 August 2006
Contents |
Generic
- Never use tabs. Use spaces instead.
- Use 72 columns (or was it 79?) maximum width whenever possible (but always in DETAILS!).
- Respect the MAINTAINER value. Don't bump maintained modules unless you got the permission from the maintainer.
DETAILS
- Use sha1: instead of md5: for SOURCE_VFY values.
- Don't insert your eMail address into the MAINTAINER field unless you are a Lunar developer.
- Prefer tar.bz2 over tar.gz tarballs (as it saves space/traffic) and prefer tar.gz over zip (or rar) packages.
DEPENDS
- If dependency B implies dependency A, only add depends B (or optional_depends B ..., depending on the dependency type).
CONFLICTS
- Remember to add a CONFLICTS to both modules that conflict with each other.
CONFIGURE
PRE_BUILD
BUILD
- Don't install files after calling devoke_installwatch.
POST_BUILD
- Don't install any files into the system.
POST_INSTALL
- Don't install any files into the system.
