--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/doc/flavours.txt	Wed Mar 28 14:58:35 2007 -0700
@@ -0,0 +1,10 @@
+
+pkg
+FILE FLAVOURS IN A PACKAGE
+
+platform
+ISA (particularly need to know i386 on i86pc vs amd64 on i86pc)
+debug/non-debug
+compatibility
+	(for shipping non-bleeding edge .so.x.y.z copies, perhaps)
+

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/doc/transaction-order.txt	Wed Mar 28 14:58:35 2007 -0700
@@ -0,0 +1,17 @@
+
+pkg
+PACKAGE TRANSACTION ORDER
+
+
+- [zfs snapshot]
+- pull bits to same filesystem
+- test transaction
+- begin operations
+- cp old to SHA-old
+- mv SHA-new to new
+- perform actions
+- complete
+
+- when are old versions discarded
+- when is snapshot discarded
+	- snapshot namespace for pkg(1M)

--- a/doc/versions.txt	Mon Mar 26 17:16:30 2007 -0700
+++ b/doc/versions.txt	Wed Mar 28 14:58:35 2007 -0700
@@ -73,6 +73,28 @@
   pkg delete on groups removes leaf packages in the group (included via
   "pkg" statements) but leaves package dependencies untouched.
 
-  
-  
+
+Co-requisite packages
+
+  We need to support a@1 <-> b@2.  This is handled as two transactions,
+  so we need to allow unresolved dependencies to exist in the
+  repository, _but_ the R = (a@1, ...) repository cannot offer a@1 until
+  it also has b@2.  And also G (a@1, b@2) group package cannot be
+  submitted.
+
+  This requirement becomes a hint for our order of operations:
+  individual package transactions, group (base and stack) transactions.
+
 
+When to increment the branch number?
+
+  On incompatible change to a private interface.
+
+  On addition of new private interfaces.
+
+  On addition of new public interfaces where the release version is
+  constrained.
+
+  Potentially on the addition of a newly delivered flavour?
+
+