From owner-svn-src-projects@FreeBSD.ORG Tue Feb 10 09:20:08 2015 Return-Path: Delivered-To: svn-src-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A4087676; Tue, 10 Feb 2015 09:20:08 +0000 (UTC) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cloud.theravensnest.org", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F820CB0; Tue, 10 Feb 2015 09:20:07 +0000 (UTC) Received: from [192.168.0.7] (cpc16-cmbg15-2-0-cust60.5-4.cable.virginm.net [86.5.162.61]) (authenticated bits=0) by theravensnest.org (8.15.1/8.14.9) with ESMTPSA id t1A9K4wD002957 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 10 Feb 2015 09:20:06 GMT (envelope-from theraven@FreeBSD.org) X-Authentication-Warning: theravensnest.org: Host cpc16-cmbg15-2-0-cust60.5-4.cable.virginm.net [86.5.162.61] claimed to be [192.168.0.7] Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Subject: Re: svn commit: r278447 - projects/release-pkg/release/packages/kernel From: David Chisnall In-Reply-To: <54D8E5CD.8050304@FreeBSD.org> Date: Tue, 10 Feb 2015 09:19:59 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: <71EFE329-6A63-4A2A-9083-BEED15991F4C@FreeBSD.org> References: <201502091025.t19APxwK057568@svn.freebsd.org> <2379227.vPTf1TCfaA@ralph.baldwin.cx> <20150209161830.GH29891@ivaldir.etoilebsd.net> <54D8E5CD.8050304@FreeBSD.org> To: John Baldwin X-Mailer: Apple Mail (2.2070.6) Cc: svn-src-projects@freebsd.org, Baptiste Daroussin , src-committers@freebsd.org X-BeenThere: svn-src-projects@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "SVN commit messages for the src " projects" tree" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2015 09:20:08 -0000 On 9 Feb 2015, at 16:52, John Baldwin wrote: >=20 > Hmm, it might be nice to choose it at runtime. Maybe I want to use > GENERIC as the main kernel so I want it at /boot/kernel, maybe I wnat = to > install the "official" FreeBSD GENERIC kernel as /boot/kernel.GENERIC = so > I'd like to be able to override the "prefix" as it were. Similarly, I > might want to install a test kernel package to /boot/test so I can use > it with nextboot without changing the machine's default kernel. In = the > case of the kernel all the bits live in one directory, so if you allow > the directory to be fungible during install that should be doable. I > can't think of other things besides the kernel that have this sort of > behavior. Would it work to have each kernel install as a unique name (e.g. = KERNEL.GENERIC-11.1r6) and a symlink that's updated to point to the most = recently installed one? I can think of a few other ports where you want = to have multiple versions installed with a suffix like this and would = ideally like the same behaviour (e.g. the llvm ports, where you might = need llvm33 installed for some dependency and llvm35 installed because = it's the latest, but would quite like symlinks from clang -> clang35 and = so on). The only issue that I can see with this approach is that you'd need to = make sure that you eventually removed old kernels if you didn't want = /boot to become full and it's not clear what the trigger should be = (remove the old one after successful boot of the new one? Perhaps we'd = want the ability to clear the old one's installed-by-user flag so that a = future pkg autoremove would delete it if it's a normal upgrade - this = might be a sensible default for anything where old and new versions = don't conflict with each other). =20 David