diff options
author | joe <joe@jerkface.net> | 2014-05-06 21:51:00 -0400 |
---|---|---|
committer | joe <joe@jerkface.net> | 2014-05-06 21:51:00 -0400 |
commit | a2956290e258368b29bd7f7a8d720e78daa57b2a (patch) | |
tree | fa4034dcd92d5c061f8d2564320b88dc8abdf097 | |
parent | 50d1895913fbbc40823b92c75b9d9f1d0a619dc1 (diff) |
corrected HACKING note
-rw-r--r-- | HACKING | 21 |
1 files changed, 16 insertions, 5 deletions
@@ -5,12 +5,23 @@ contributers to the kiki project. | |||
5 | === Dependencies Policy === | 5 | === Dependencies Policy === |
6 | * The current approach in terms of library dependencies is as follows: | 6 | * The current approach in terms of library dependencies is as follows: |
7 | 7 | ||
8 | 1) Use the api of packages most recently published to hackage | 8 | 1) It should work with libraries bundled with Debian on both |
9 | even though they may not be functional in debian/stable. | 9 | Debian Wheezy and Debian Jessie. |
10 | 10 | ||
11 | 2) Attempt to build with only haskell platform packages which do not require | 11 | 2) Development occurs on Jessie first, and then the build is |
12 | versions of external libraries beyond what is distributed on debian/stable, and | 12 | backported to Wheezy. |
13 | use #if directives to effectively backport the code base to older apis. | 13 | |
14 | 3) When backporting, it is preferred to use libraries available | ||
15 | in Wheezy unless the effort would be too great and then it is | ||
16 | prefered to use dependency versions that are already packaged for | ||
17 | Jessie. | ||
18 | |||
19 | 4) Exceptions can be made for must-have features in libraries | ||
20 | not packaged for Jessie. In which case, it is prefered to use | ||
21 | a version packaged for Sid, and if not available in Sid, | ||
22 | Experimental, and if not Experimental, then whatever is currently | ||
23 | available through cabal/hackage. And finally as a last resort, | ||
24 | whatever is available via git. | ||
14 | 25 | ||
15 | * This approach keeps the code base fresh without limiting it's ease of install | 26 | * This approach keeps the code base fresh without limiting it's ease of install |
16 | and utility on existing systems. | 27 | and utility on existing systems. |