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 EE33D1381FA for ; Mon, 5 May 2014 17:04:37 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 59103E0ACD; Mon, 5 May 2014 17:04:37 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id C8B73E0ACD for ; Mon, 5 May 2014 17:04:36 +0000 (UTC) Received: from vereniki.bit-level.net (unknown [IPv6:2a01:7e00::f03c:91ff:fedf:bae1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: pchrist) by smtp.gentoo.org (Postfix) with ESMTPSA id 86FA33402B3; Mon, 5 May 2014 17:04:35 +0000 (UTC) Date: Mon, 5 May 2014 20:04:32 +0300 From: Panagiotis Christopoulos To: gentoo-mips@lists.gentoo.org Cc: releng@gentoo.org Subject: Re: [gentoo-mips] Reducing the number of the MIPS supported stages Message-ID: <20140505170432.GA22867@earth.members.linode.com> References: <53679ACC.3000809@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-mips@lists.gentoo.org Reply-to: gentoo-mips@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cNdxnHkX5QqsyA0e" Content-Disposition: inline In-Reply-To: <53679ACC.3000809@gentoo.org> User-Agent: Mutt/1.5.23 (2014-03-12) X-Archives-Salt: 55b26a1e-373b-4392-8bbe-7047355ca264 X-Archives-Hash: e2bc7ea294bc0adb6355f3120039199a --cNdxnHkX5QqsyA0e Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 15:06 Mon 05 May , Markos Chandras wrote: > Hi all, Hi, > ...=20 > This takes quite a bit of time for all stages to be built (by the time=20 > everything is built, we are one month passed the time the snapshot was=20 > taken). How about stop building stages for mips1, mips3 and mips4? We=20 > keep the existing stages on the mirrors but we will no longer update=20 > them (or maybe we do on per user or per case basis). I understand there= =20 > is hardware for these ISAs but how often do people actually use the new= =20 > stages? >=20 > Just to be clear, I am not suggesting for the team to stop supporting=20 > these ISAs but to stop building new stages and let the users of such=20 > ISAs, grab an old stage3 and do the update themselves if needed. >=20 > This will free up some hardware resources for building different stages= =20 > for the newer ISAs (maybe more non-multilib n32 and n64 variants etc) >=20 > What does everyone think? I agree. If we don't have the resources to build everything for everyone, l= ets just build what is mainstream at the moment. I don't know catalyst's intern= als or how painful it would be to update the whole set once per year or a bit l= onger, but it could be nice, because I'm not sure how possible would be to update a stage3 afte= r > 1-2 years. But again, because I'm not in the MIPS industry, so can't say whether peopl= e are really using the older ISAs stages, if you suspect nobody is using them just do as= you say and stop updating them, and we build any upon request. Panagiotis --=20 Panagiotis Christopoulos ( pchrist ) ( Gentoo Lisp Project ) --cNdxnHkX5QqsyA0e Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iIoEABECAEoFAlNnxKBDFIAAAAAAEgAocGNocmlzdEBnZW50b28ub3JnMEE4ODEw MzBDRDQ0RkRCMkEwMDFFNzZFM0FDNTc5QjkxQkMwMzY1NgAKCRA6xXm5G8A2VgM5 AJ9ZPcAplGvo3xyhUeKUAD/tZfojwACgi0dSxrVi9PTvLes3C3Gs42UIGAA= =E0+o -----END PGP SIGNATURE----- --cNdxnHkX5QqsyA0e--