Gentoo Archives: gentoo-soc

From: Stanislav Ochotnicky <sochotnicky@×××××.com>
To: gentoo-qa@l.g.o
Cc: gentoo-soc@l.g.o
Subject: [gentoo-soc] [GSoC-status] Collagen - database schema and further changes
Date: Fri, 26 Jun 2009 12:51:23
Message-Id: 20090626125103.GA13253@w0rm
1 So another (if a bit late) status update for Tree-wide collision
2 checking and files database is coming.
3
4 I don't plan on having any major architectural changes from this point
5 on (I will update docs on soc.gentooexperimental.org during the
6 weekend). We have matchbox as master server and tinderboxes as compile
7 slave. Previously mentioned binary host is not yet implemented at all
8 since we want to get to actually compiling stuff as soon as possible and
9 speed is a bit down the list for now.
10
11 We have basic database model for storing information collected by
12 tinderboxes ready (doc/ddl.sql - it is a dump of postgresql database,
13 model is at gentooexperimental web).
14 There are few changes that are not included there yet, such as
15 tinderbox slave table with information about them. There will definitely
16 be more changes to ddl as we go, but hopefully nothing major.
17
18 I hit a few minor issues with chroot for compilation creation. Whole
19 process goes like this:
20 (not chrooted yet)
21 * We get information about use flags/dependencies etc for the package
22 * Call external shell script to prepare chroot and mount proc and dev
23 * chroot and call portage.doebuild(...)
24
25 Now the external shell script I created uses official stage file to
26 create base chroot, then rsyncs /usr/portage to chroot. From this point
27 on further customization of BASE chroot is possible. Issue is that we
28 need to have same version of portage in BASE_CHROOT as we have on
29 tinderbox, otherwise things can get really ugly. Chroot preparation
30 script will therefore see some changes. I am looking into options for
31 making sure that everything is set up correctly. One easy possiblity is
32 to manually change BASE_CHROOT after basic setup by script. Better
33 solution is to integrate catalyst into chroot creation.
34
35
36 Now it's one big puzzle with one bit missing here, one bit missing
37 there. But it's slowly starting to come together. Fortunately I have
38 tried most things as small POCs and I am starting to see light at the
39 end of the tunnel (pretty far away but visible).
40
41
42 P.S. In case it's not so obvious, repository is here:
43 git://git.overlays.gentoo.org/proj/collagen.git
44
45 --
46 Stanislav Ochotnicky
47 Working for Gentoo Linux http://www.gentoo.org
48 Implementing Tree-wide collision checking and provided files database
49 http://soc.gentooexperimental.org/projects/show/collision-database
50 Blog: http://inputvalidation.blogspot.com/search/label/gsoc
51
52
53 jabber: sochotnicky@×××××.com
54 icq: 74274152
55 PGP: https://dl.getdropbox.com/u/165616/sochotnicky-key.asc

Replies

Subject Author
[gentoo-soc] Re: [GSoC-status] Collagen - database schema and further changes Stanislav Ochotnicky <sochotnicky@×××××.com>