On Fri, Jan 18, 2013 at 9:41 AM, Michael Weber <[email protected]> wrote:
> On 01/18/2013 09:28 AM, Benedikt Böhm wrote: > > but - and that's quite important i guess - i only use my own clone of > > the portage tree which i sync from time to time and i also keep > > different versions stable, etc. > HEAVY USER! But you have full control. > Do you have any sophisticated mechanism to detect tree breakage (i.e. us > f*** up), like Samuli replying -commit to -dev or irc activity? > > Or do you simply delay commit? (re-schedule on weekends/nights) > i manually sync with the gentoo-x86 repo from time to time (except security issues, which i sync as soon as they are fixed) i have no automated way to detect any tree breakage, but when i sync the complete tree i do extensive manual testing on a handfull of machines (either staging machines, or ones that are not really important) but the main reason i even have a clone is to sync updates in batches. it's really a hassle to keep servers in sync when changes to gentoo-x86 happen any other minute. i also need to adapt my chef cookbooks for some updates, so i do it all in one batch (sync, test, adapt, test, deploy) > Delaying stabilization seems legit, but on Gentoo-stable ?! > it's not really about delaying stabilization ... there is quite a big list of packages in my repo where i always stabilize the latest version(s) even if gentoo-x86 is unstable. e.g. i've stabled openrc a looong time before gentoo-x86 had it stable, etc. it's also a lot easier to add new packages because i don't have to support everything and the kitchen sink ... my repo just supports amd64 and it also has quite a few binary ebuilds which would not be a good fit for gentoo-x86 if you're interested, it's all on github: https://github.com/zentoo/zentoo(all the sync tools are in the script directory and were initially copied from the prefix guys, but have been heavily modified since ...) Cheers, Bene
