schorsch_76
Guru
Joined: 19 Jun 2012
Posts: 450
|
 Posted: Fri Jul 03, 2015 9:01 am Post subject: Thoughts on a buildd daemon for gentoo |
 |
|
As i thought about the Problems on this [1] thread, i made some Internet searches and collected some ideas about a buildd for gentoo.
| Quote: | | 7. automated building (something like exherbo already does, so I don't mean a manual tinderbox) |
My idea for a gentoo buildd would be:
- seed a target
- Prevent Network Access for the buildd
- use receipes to check
- unseed the target
Seed stage:
- starting at a empty chroot
- dearchive a stage3
- bind /dev /sys /proc
- clone the required portage tree
- set up a seperate Network stack to Isolate it and prevent it from downloading stuff (CONFIG_NET_FS on the host)
- Setup the mirror to a local distfiles Folder (readonly for the buildd)
Now we would need "receipes". Like: "this combination of use flags/keywords/Profile and build this Targets"
Example recipe:
- stage3_20150703 and the portage tree of this date
- Profile: Gnome/systemd
- Targets: Gnome-meta / kde-meta / xfce4-meta / ...
Now we could build all this stuff and collect the output and results. Build failures are caught and mailed to an email
Fetch failures would indicate a live ebuild in the tree or a missing file on the distfiles mirror.
For each receipe the buildd would "unseed the target", "seed it again" and build the receipes again.
I looked at other distros what they do like Debian (which i know best from the other distros) . From exherbo i could not find a description of their buildd.
What things are needed? What things a gentoo buildd needs to fullfill?
[1] https://forums.gentoo.org/viewtopic-t-1020810-highlight-.html
_________________
// valid again: I forgot about the git access. Now 1.2GB big. Start: 2015-06-25
git daily portage tree
Web: https://github.com/schorsch1976/portage
git clone https://github.com/schorsch1976/portage |
|
Portage & Programming
