From: Stanislav Ochotnicky <sochotnicky@gmail.com>
To: gentoo-qa@lists.gentoo.org
Cc: gentoo-soc@lists.gentoo.org
Subject: [gentoo-qa] [GSoC-status] Collagen - database schema and further changes
Date: Fri, 26 Jun 2009 14:51:03 +0200 [thread overview]
Message-ID: <20090626125103.GA13253@w0rm> (raw)
[-- Attachment #1: Type: text/plain, Size: 2574 bytes --]
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@gmail.com
icq: 74274152
PGP: https://dl.getdropbox.com/u/165616/sochotnicky-key.asc
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2009-06-26 12:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 12:51 Stanislav Ochotnicky [this message]
2009-07-03 15:41 ` [gentoo-qa] Re: [GSoC-status] Collagen - database schema and further changes Stanislav Ochotnicky
2009-07-09 21:36 ` Stanislav Ochotnicky
2009-07-17 13:39 ` Stanislav Ochotnicky
2009-07-25 22:50 ` Stanislav Ochotnicky
2009-07-31 9:44 ` Stanislav Ochotnicky
2009-08-07 8:12 ` Stanislav Ochotnicky
[not found] ` <20090807081410.GB29277@w0rm.ynet.sk>
2009-08-15 21:10 ` Stanislav Ochotnicky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090626125103.GA13253@w0rm \
--to=sochotnicky@gmail.com \
--cc=gentoo-qa@lists.gentoo.org \
--cc=gentoo-soc@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox