From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.54) id 1F3pHH-0004Yr-RJ for garchives@archives.gentoo.org; Tue, 31 Jan 2006 06:46:12 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id k0V6jSxm032486; Tue, 31 Jan 2006 06:45:28 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id k0V6hdYa018673 for ; Tue, 31 Jan 2006 06:43:39 GMT Received: from [24.182.19.146] (helo=[192.168.1.101]) by smtp.gentoo.org with esmtpa (Exim 4.54) id 1F3pEo-0000B1-ND for gentoo-dev@lists.gentoo.org; Tue, 31 Jan 2006 06:43:38 +0000 Message-ID: <43DF07EB.3060607@gentoo.org> Date: Mon, 30 Jan 2006 22:47:07 -0800 From: Joshua Jackson User-Agent: Mail/News 1.5 (X11/20060114) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: Unmasking modular X References: <43D5D1E4.9020801@gentoo.org> <200601252118.28410.jstubbs@gentoo.org> <43D87585.2000206@gentoo.org> <200601261626.15067.jstubbs@gentoo.org> <43D87EFB.5080505@gentoo.org> <20060131024137.GA19351@aerie.halcy0n.com> <43DEFD31.6010500@gentoo.org> In-Reply-To: <43DEFD31.6010500@gentoo.org> X-Enigmail-Version: 0.93.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: 93cd4231-91c9-4062-a654-eb59c701c0d2 X-Archives-Hash: 4c9e0719087d4f38a174d01901cfd8d9 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Donnie Berkholz wrote: > Joshua Jackson wrote: >> I will have to agree that this change has made it a pain to mark >> anything >> stable. I had 4 out of the 6 I did today bail out because of this. >> I took the >> simple easy fix and removed the check to stabalize the packages I >> needed to. I >> know we have people who want modular X yesterday, but causing >> trouble for dev's >> going about business that doesn't involve the modular problems >> directly is only >> going to cause resentment and frustration to all the teams involved. > > Why is the simple fix not copying over the already fixed > dependencies in the latest ebuild? It's not as if that's a lot of > work. That's the intent of this failure -- to avoid flyby commits by > people when they could just fix the deps (which are already > available in ~arch) while they're there. > > Thanks, > Donnie In the oldest version of the package (as all these were), I don't see much point in the change. They will be removed within a fairly short amount of time. Secondary, you are suggesting that any dev who comes across a modular x problem to fix it..even if this is a direct violation of the guidelines set forth in the documentation? I'm curious as to why you want potentially 200+ dev's to violate it, to push modular so quickly? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFD3wfrSENan+PfizARApkUAJ4/Rfr/iMwZMD1lCkhwBnGH+BhUVwCdHqsD Rc97k6+FBAKp59MAa2t16Ig= =P92T -----END PGP SIGNATURE----- -- gentoo-dev@gentoo.org mailing list