33 lines
1.3 KiB
Plaintext
33 lines
1.3 KiB
Plaintext
-Packages adhere to the same basic set of rules as standard KISS packages.
|
|
|
|
-However, indentation is three spaces, instead of four.
|
|
|
|
-The only package from Core that should be listed as an explicit dependency of
|
|
anything is cURL; this is because cURL is not absolutely necessary.
|
|
|
|
-Packages will only be accepted if they are available from an HTTPS source;
|
|
a good place to find secure sources is the Debian repositories.
|
|
|
|
-Packages are expected to provide the bare-minimum necessary to get a program
|
|
to run. In the event that there are multiple options for a given program
|
|
(e.g what UI toolkit to use), always take the option that results in the
|
|
fewest overall dependencies. Remember that forking is encouraged.
|
|
|
|
-Internationalization should always be disabled by default.
|
|
|
|
-Unless necessary for an existing package, arbitrary libraries will not be
|
|
accepted.
|
|
|
|
-Packages for software that is not generally used by the community will not be
|
|
accepted. It's a community repository, not your personal one.
|
|
|
|
-New packages will not use install -d, nor shall they use sed -i. Neither of
|
|
these are portable. The former can be handled with -D, and the latter can
|
|
be accomplished using redirects.
|
|
|
|
-Packages built from Git will be stored under community/rolling
|
|
|
|
-Packages built from tarballs will be stored under community/stable
|
|
|
|
|