Gentoo Archives: gnap-dev

From: codesite-noreply@××××××.com
To: gnap-dev@l.g.o
Subject: [gnap-dev] [gnap-dev commit] r130 - wiki
Date: Mon, 07 Jul 2008 14:32:31
Message-Id: 0016e650965e60d05c04516ff1eb@google.com
Author: vomacko
Date: Mon Jul  7 07:31:53 2008
New Revision: 130

Added:
   wiki/gnap_glsa_proposal.wiki

Log:
Created initial glsa integration description page

Added: wiki/gnap_glsa_proposal.wiki
==============================================================================
--- (empty file)
+++ wiki/gnap_glsa_proposal.wiki	Mon Jul  7 07:31:53 2008
@@ -0,0 +1,9 @@
+#summary One-sentence summary of this page.
+
+= Introduction =
+Here, I would like to describe initial thoughts about integration of 
GLSA checks into GNAP and further steps in this area
+
+
+= Details =
+
+I would like to integrate glsa_check ( both update ability and 
notification ability) for existing gnap_make tool. We should be able to 
update/regenerate existing core builds and if possible use also 
extensions for that. We can make separate script with only "gnap_glsa" 
functionality, with shared codebase with gnap_make or we can integrate 
it in gnap_make directly. Since there will be large change in 
portage-2.2 GLSA abilities,we need to be more flexible. That's why I 
introduced thought of gnap_run, which will do what gnap_make do 
(including same params etc.) but can do whatever you want to do in 
chrooted environment of your embedded build. It could help us with 
debugging catalyst builds. Now we have to make all the "chroot work" 
done manually. It would look like gnap_run -t all "glsa-check -l"  . I 
will also have to provide path to recent portage tree (we need recent 
glsa files)
\ No newline at end of file
-- 
gnap-dev@l.g.o mailing list