new column `architecture_compatibilities`.`fully_compatible` to show wether all built packages will be compatible in the indicated way (in contrast to: instruction set of arch $x is a subset of arch $y) - beware of linking against libraries compiled for different architectures!

1 files changed, 4 insertions, 3 deletions

diff --git a/misc/database-layout.dump b/misc/database-layout.dump
index 1e67bda..1aef0c2 100644
--- a/misc/database-layout.dump
+++ b/misc/database-layout.dump
@@ -339,6 +339,7 @@ architecture_compatibilities	CREATE TABLE `architecture_compatibilities` (
 	 `id` mediumint(9) NOT NULL AUTO_INCREMENT,
 	 `built_for` smallint(6) NOT NULL,
 	 `runs_on` smallint(6) NOT NULL,
+	 `fully_compatible` bit(1) NOT NULL,
 	 PRIMARY KEY (`id`),
 	 UNIQUE KEY `content` (`built_for`,`runs_on`),
 	 KEY `architecture_compatibilities_ibfk_2` (`runs_on`),
@@ -651,9 +652,9 @@ INSERT INTO `architectures` VALUES
   (1,'any'),
   (2,'i686');
 INSERT INTO `architecture_compatibilities` VALUES
-  (1,1,1),
-  (3,1,2),
-  (2,2,2);
+  (1,1,1,'1'),
+  (2,2,2,'1'),
+  (3,1,2,'1');
 INSERT INTO `dependency_types` VALUES
   (2,'run','1','1'),
   (3,'check','\0','\0'),