List Archive: gnap-dev
Note: Due to technical difficulties, the Archives are currently not up to date.
provides an alternative service for most mailing lists.c.f. bug 424647
Date: Mon Jul 7 07:31:53 2008
New Revision: 130
Created initial glsa integration description page
--- (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
\ No newline at end of file
firstname.lastname@example.org mailing list