doc/es-requirements.txt
changeset 17 bcdb1d388a7f
parent 16 34fa0ef929b0
child 18 96ef08ceb10b
--- a/doc/es-requirements.txt	Thu Apr 05 17:41:56 2007 -0700
+++ b/doc/es-requirements.txt	Fri Apr 06 12:35:36 2007 -0700
@@ -21,6 +21,13 @@
 its root directory, and its parent image (for satisfying non-relocatable
 packages).
 
+Question for ES folks: does "the system" need to (or want to) know about
+non-root installs in order to be able to patch / upgrade them along with
+normal installs (or send out reminders to do so), or will non-root installs
+be completely up to the user to manage?  I can see a site policy that
+requires security patches even for non-root installs; this would require
+such installations to register with the system so they can be found.
+
 Not sure how to proceed on the Windows requirement.  Most of the current
 design is portable across POSIX/ELF systems.