From owner-freebsd-current@freebsd.org Thu Jan 19 19:58:47 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8BAE9CB891B for ; Thu, 19 Jan 2017 19:58:47 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BCA91B03; Thu, 19 Jan 2017 19:58:47 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id 22F9D1F1C; Thu, 19 Jan 2017 19:58:46 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Thu, 19 Jan 2017 19:58:43 +0000 From: Glen Barber To: Andreas Nilsson Cc: "O. Hartmann" , Matthias Apitz , Current FreeBSD Subject: Re: ISO image: where is the CLANG compiler? Message-ID: <20170119195843.GI1451@FreeBSD.org> References: <20170118101915.523d7d7b@freyja.zeit4.iv.bundesimmobilien.de> <20170118123515.GE58505@zxy.spb.ru> <20170118160801.229b4134@freyja.zeit4.iv.bundesimmobilien.de> <20170118153832.GA6905@c720-r292778-amd64> <20170118203726.7dea0515@thor.intern.walstatt.dynvpn.de> <20170119055816.GA2184@c720-r292778-amd64> <20170119101636.5537f4fd@freyja.zeit4.iv.bundesimmobilien.de> <20170119191000.GG1451@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Az4VpBrmI9+OyhK/" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.0-STABLE amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer X-Spidey-Sense: Uh oh, Peter logged in User-Agent: Mutt/1.7.1 (2016-10-04) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Jan 2017 19:58:47 -0000 --Az4VpBrmI9+OyhK/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 19, 2017 at 08:50:34PM +0100, Andreas Nilsson wrote: > On Thu, Jan 19, 2017 at 8:10 PM, Glen Barber wrote: > > I do want to weigh in here and inform I am actively watching this > > thread. clang(1) is not in disc1.iso or bootonly.iso because the > > MK_TOOLCHAIN knob is disabled in the targets that generate them. This > > has actually been the case for quite some time for these images. > > > > dvd1.iso does contain clang, but very rarely (if ever, actually) are > > there dvd1.iso images produced for development snapshots. This is, in > > part, solely because of the additional space/bandwidth required on the > > mirrors (not just mirrors controlled by the Project, but third-party > > mirrors as well). > > > > I am working on splitting out how the memstick.img and disc1.iso images > > are produced, but ran into a problem which I'm looking into a workaround > > that is backwards-compatible. Since for USB images, a 700MB limit does > > not make sense, and right now it just so happens that the memstick.img > > is created from the same contents of disc1.iso. > > > > I know this does not help with the immediate issue, but wanted to chime > > in with I do see and understand the larger issue, and am working on > > a more long-term resolution instead of a one-line workaround. > > > > > Good to see discussion, but my 5c is: do not enlarge regular install medi= a, > it is hefty enough. I'd rather see it shrink, although without the > limitations of old cd's rescue-env. >=20 > Install media is install media, not live image. Live usb-sticks are so ea= sy > to do on your own, why waste the Projects storage and bandwidth on it? >=20 For cases like what initiated this thread, actually. But, I'm not looking to increase the disc1.iso size, but separate the disc1.iso and memstick.img targets, which then can be created from different userland environments (one with /usr/bin/clang and one without, for example). But, I do agree with you that keeping the downloadable installer medium as small as possible (while still being usable for "rescue" cases like this) is ideal. Glen --Az4VpBrmI9+OyhK/ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCAAGBQJYgRpzAAoJEAMUWKVHj+KTOaQP/2H814QLrFM018X7aT7IcD5h fDiyYgGhrGPyxLLSwyWMyPsajYss3dbtnfN/YEt3tyDXzW0M9N6HtcjeaxiTZeVb vJ6zqTs7LKqkObB8FFm6xkoOpIa2KhHXvQdAXz7dmDXaFnZQIHV0r/zV7trtSDwb T2Yi9cQgudzezIUPeGs85VtPZ1GLAT4/OUbikVjyURWgDSapuS1MmH8XwHje9AGG KG7zgHFhkIxPtxIuJDjOG2PKL+YAr9WsTotmJg5JHTH5NqzdQgKMcS1DWnMJeoBx GDcXn1LrVuJvdCV22jPulkWIlwDzK1NoPpp/Um1G9aJUFV02gXcbKx/7Bo1qEv5q VG7uK2ynlIVLFYExa8kSI2qmdyu7Mo+bIWHmeBxk5ceagOl/+AHve5J0MnpStWrj gG8B7DaChggRSotnFEFkHRMXEHnGMsQBD6b7r/qGeUll++FFLO4eBxVN0ccj+gvD 5rsGxrelSaB3LvaFoX1Bh0ZgLtNepxu8zFKBYSTGXgoWWKn0dFXJEuM3jIpFTz8h XKsbKglsPlLKNL0w1izvKcC26/YdAuVlJxK3gV+d2zxqIRZUQNKmt63HwA0hLmpX AhogCzw1rwtK5NLEKnkfgAzZv854BtOsIGO7BeNzYWqA8EPhDk7ibxE8pInsYHY/ t74GmcEFNd3ssYNGNFU9 =uE91 -----END PGP SIGNATURE----- --Az4VpBrmI9+OyhK/--