From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 1BCB6138010 for ; Sun, 24 Mar 2013 10:04:21 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E391CE07A4; Sun, 24 Mar 2013 10:04:12 +0000 (UTC) Received: from mail-ia0-f170.google.com (mail-ia0-f170.google.com [209.85.210.170]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 069AEE0552 for ; Sun, 24 Mar 2013 10:04:11 +0000 (UTC) Received: by mail-ia0-f170.google.com with SMTP id h8so4739319iaa.1 for ; Sun, 24 Mar 2013 03:04:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=oy1cDoR7JYqSSt0I/0dYtgq42+T7JOlVLdQMVf2pnZM=; b=tur+0j+GvFUpz/oN44EwNC2vAXgaJqI3SxFaj3QWR93WhiEPgbRJ3HmSaytGivzQEK D7WDZ6B624QzagjhRrW/9W8ep2HJInajJhKtEnd/vG5SyzvukCuz8icJ3IRa9eXZKWbm 492fAJNGgBERlPRxv9B4PdmJLfe8uAyIj2Nm1okfr4JM+GEOCVZpZLlLm5uyR+g4xqNk FFQ3gzFS2m5nV6vDEfa+pPCz5etCyn/m86hrW/4IVAee/F+wPYdc4reJDskclIb+BHnc piUxKguccfjv5fIZ72DGXzO04/LugRgnUT2/rwbhvpwD7uU3QvX3m4IgctHus6CPa6Vp cPaQ== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.50.72.3 with SMTP id z3mr4835588igu.47.1364119451299; Sun, 24 Mar 2013 03:04:11 -0700 (PDT) Sender: freemanrich@gmail.com Received: by 10.64.135.36 with HTTP; Sun, 24 Mar 2013 03:04:11 -0700 (PDT) In-Reply-To: References: <1364062009.1933.11.camel@belkin4> <201303232128.35768.dilfridge@gentoo.org> <201303240029.34053.dilfridge@gentoo.org> <514E540D.1090303@gmail.com> <514EAC06.7000107@gentoo.org> Date: Sun, 24 Mar 2013 06:04:11 -0400 X-Google-Sender-Auth: -MJCXm1jpljh1Up1MysnRy56gZE Message-ID: Subject: Re: [gentoo-dev] Re: New install isos needed From: Rich Freeman To: gentoo-dev Content-Type: text/plain; charset=ISO-8859-1 X-Archives-Salt: 30186d84-e7c7-476e-9200-1f3a0f03d442 X-Archives-Hash: 5fe086cbfe86d4be4fbf502202204e5f On Sun, Mar 24, 2013 at 5:05 AM, Duncan <1i5t5.duncan@cox.net> wrote: > I've wondered for years why gentoo invests all that effort into creating > its own install media, when there's many dedicated projects out there > whose whole purpose is live install/rescue media. Tend to agree. I'd focus more on keeping stage3s up-to-date. After we perform fairly significant system package changes (the kind that involve news items) there is a tendency for stage3s to take even weeks on some occasions to get updated. That means that the first experience of a new Gentoo user is to get to do a udev migration, resolve blocks, read news items, or whatever. Ideally these big changes should be coordinated with releng, but maybe that isn't realistic. Our stage3s should still catch up reasonably quickly. I haven't run my gentoo bootstrap scripts, but as of a few weeks ago the x86 one was still having to manually uninstall module-init-tools. That may be fixed now, but in general it has been my observation that automated builds of complex Gentoo systems (kde, gnome with desktop profiles) tend to fail more often than not due to one problem or another. Ideally it should just involve setting the appropriate profile and emerging the appropriate meta-package. In practice you have to set a few USE flags as well (which for whatever reason the profile doesn't set). However, much of the time you end up having to fix missed dep keywords, blockers, etc. I do try to log these issues when I spot them, but haven't generally done this if the issue is simply that the stage3 is a few weeks old (I don't mind doing that, but I suspect it won't really be anything releng isn't already aware of). For an educational experience unpack a stage3 in a chroot and try to emerge kde or gnome. Then try it again two weeks later. This is what our new users experience. Rich