Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-qa
Navigation:
Lists: gentoo-qa: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-qa@g.o
From: Stanislav Ochotnicky <sochotnicky@...>
Subject: [GSoC-status] Collagen - database schema and further changes
Date: Fri, 26 Jun 2009 14:51:03 +0200
So another (if a bit late) status update for Tree-wide collision 
checking and files database is coming.

I don't plan on having any major architectural changes from this point
on (I will update docs on soc.gentooexperimental.org during the
weekend). We have matchbox as master server and tinderboxes as compile
slave. Previously mentioned binary host is not yet implemented at all
since we want to get to actually compiling stuff as soon as possible and
speed is a bit down the list for now.

We have basic database model for storing information collected by
tinderboxes ready (doc/ddl.sql - it is a dump of postgresql database,
model is at gentooexperimental web).
There are few changes that are not included there yet, such as 
tinderbox slave table with information about them. There will definitely
be more changes to ddl as we go, but hopefully nothing major.

I hit a few minor issues with chroot for compilation creation. Whole
process goes like this:
(not chrooted yet)
 * We get information about use flags/dependencies etc for the package
 * Call external shell script to prepare chroot and mount proc and dev
 * chroot and call portage.doebuild(...)

Now the external shell script I created uses official stage file to
create base chroot, then rsyncs /usr/portage to chroot. From this point
on further customization of BASE chroot is possible. Issue is that we
need to have same version of portage in BASE_CHROOT as we have on
tinderbox, otherwise things can get really ugly. Chroot preparation
script will therefore see some changes. I am looking into options for
making sure that everything is set up correctly. One easy possiblity is
to manually change BASE_CHROOT after basic setup by script. Better
solution is to integrate catalyst into chroot creation. 


Now it's one big puzzle with one bit missing here, one bit missing
there. But it's slowly starting to come together. Fortunately I have
tried most things as small POCs and I am starting to see light at the
end of the tunnel (pretty far away but visible).


P.S. In case it's not so obvious, repository is here: 
        git://git.overlays.gentoo.org/proj/collagen.git

-- 
Stanislav Ochotnicky
Working for Gentoo Linux http://www.gentoo.org
Implementing Tree-wide collision checking and provided files database
http://soc.gentooexperimental.org/projects/show/collision-database
Blog: http://inputvalidation.blogspot.com/search/label/gsoc


jabber: sochotnicky@...
icq: 74274152
PGP: https://dl.getdropbox.com/u/165616/sochotnicky-key.asc
Attachment:
pgpVPtAz0Z1Dg.pgp (PGP signature)
Replies:
Re: [GSoC-status] Collagen - database schema and further changes
-- Stanislav Ochotnicky
Navigation:
Lists: gentoo-qa: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
[GSoC-status] Tree-wide collision checking and files database
Next by thread:
Re: [GSoC-status] Collagen - database schema and further changes
Previous by date:
Re: [gentoo-soc] [GSoC-status] Tree-wide collision checking and files database
Next by date:
Re: [GSoC-status] Collagen - database schema and further changes


Updated Aug 26, 2011

Summary: Archive of the gentoo-qa mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.