[newdak/master] Dependencies, old code

[Joerg Jaspert <joerg@debian.org>]

Want to check depends much earlier.
Also mention old code.

Signed-off-by: Joerg Jaspert <joerg@debian.org>
---
 feature.txt |   17 ++++++++++++++++-
 1 files changed, 16 insertions(+), 1 deletions(-)

diff --git a/feature.txt b/feature.txt
index 5820c91..46e9e93 100644
--- a/feature.txt
+++ b/feature.txt
@@ -19,6 +19,9 @@ When we are done with one, mark it X and add the done date too.
 If you work on something and it takes longer - mark it.
 
 
+Hint: Don't write down features which are in current dak. Only new
+ones. Unless they should be changed in some way.
+
 Also, do look into old dak doc/TODO, it does have some nice hints what
 to avoid/do.
 
@@ -215,7 +218,7 @@ General Archive Issues
 
 # From here on I just write down features in a "per tool" based
 # sectioning. Of course this is based on the old dak and the tools we
-# had there. It doesn't neccessarily mean that has to end up in the same
+# have there. It doesn't neccessarily mean that has to end up in the same
 # way in newdak. But it helps for writing here.
 # [Ganneff]
 
@@ -235,3 +238,15 @@ process-new
 process-unchecked, process-accepted
 -----------------------------------
 [See above for NiV2 as a general issue touching these]
+
+ + Check Dependencies. [Ganneff] Mon, 08 Sep 2008 21:54:34 +0200
+   At upload time, when we first process the package, another check
+   should run that verifies that Depends:, Recommends: and
+   Build-Depends[-Indep] to be valid and existant (including version
+   constraints). Obviously less strict for contrib and non-free.
+
+   Should reject on missing / not full-fillable ones and warn on useless
+   version constraints (meaning we have a version which is in stable, no
+   need to declare it).
+
+ 
-- 
1.5.6.3