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 4D6701382C5 for ; Fri, 24 Jun 2016 05:21:03 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 6C71AE0AA6; Fri, 24 Jun 2016 05:21:00 +0000 (UTC) Received: from mout02.posteo.de (mout02.posteo.de [185.67.36.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id F421CE0AA6 for ; Fri, 24 Jun 2016 05:20:59 +0000 (UTC) Received: from submission (posteo.de [89.146.220.130]) by mout02.posteo.de (Postfix) with ESMTPS id E24DB20B5A for ; Fri, 24 Jun 2016 07:20:54 +0200 (CEST) Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 3rbRW80cPgzynN; Fri, 24 Jun 2016 07:20:52 +0200 (CEST) Date: Fri, 24 Jun 2016 07:19:26 +0200 From: Felix Janda To: Lei Zhang Cc: gentoo-musl@lists.gentoo.org Subject: Re: [gentoo-musl] How is the musl based stage3 tarball made? Message-ID: <20160624051926.GA448@nyan> References: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo musl list X-BeenThere: gentoo-musl@gentoo.org X-BeenThere: gentoo-musl@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.1 (2016-04-27) X-Archives-Salt: 3076e97f-6b8d-409b-aa7a-9a2396b9bb11 X-Archives-Hash: 95dd6bf58f5f69e4b54ca65409da5a6f > Could someone shed light on how the stage3-amd-musl-vanilla-* tarball > is made? It could give me a better understanding of the workflow. You can find the scripts automating catalyst here: https://gitweb.gentoo.org/proj/releng.git/tree/tools-musl They generate the spec files from a template and let catalyst run several times in the background. Cheers, Felix