From owner-freebsd-current@FreeBSD.ORG Sun Jul 14 06:45:58 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7BC79B28; Sun, 14 Jul 2013 06:45:58 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id 487A0765; Sun, 14 Jul 2013 06:45:57 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.16]) by ltcfislmsgpa04.fnfis.com (8.14.5/8.14.5) with ESMTP id r6E6juw7006136 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sun, 14 Jul 2013 01:45:57 -0500 Received: from LTCFISWMSGMB21.FNFIS.com ([10.132.99.23]) by LTCFISWMSGHT05.FNFIS.com ([10.132.206.16]) with mapi id 14.02.0309.002; Sun, 14 Jul 2013 01:45:56 -0500 From: "Teske, Devin" To: Garrett Wollman Subject: Re: [HEADSUP] No more pkg_install on HEAD by default Thread-Topic: [HEADSUP] No more pkg_install on HEAD by default Thread-Index: AQHOgFlREhI/XtjETUan8/QjEhM8pplkDrOA Date: Sun, 14 Jul 2013 06:45:54 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D7201FC5019@ltcfiswmsgmb21> References: <20130712231637.GS85556@ithaqua.etoilebsd.net> <13CA24D6AB415D428143D44749F57D7201FC2DBD@ltcfiswmsgmb21> <20130713080732.GV85556@ithaqua.etoilebsd.net> <13CA24D6AB415D428143D44749F57D7201FC3AA2@ltcfiswmsgmb21> <13CA24D6AB415D428143D44749F57D7201FC3C92@ltcfiswmsgmb21> <13CA24D6AB415D428143D44749F57D7201FC3FAA@ltcfiswmsgmb21> <201307140613.r6E6Dsov002016@hergotha.csail.mit.edu> In-Reply-To: <201307140613.r6E6Dsov002016@hergotha.csail.mit.edu> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.126] Content-Type: text/plain; charset="us-ascii" Content-ID: <90DC4C6200470542BC36BF0A8E654C72@fisglobal.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-07-14_01:2013-07-12,2013-07-14,1970-01-01 signatures=0 Cc: Devin Teske , "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Devin Teske List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Jul 2013 06:45:58 -0000 On Jul 13, 2013, at 11:13 PM, Garrett Wollman wrote: > In article <20130714054840$7f8f@grapevine.csail.mit.edu>, > dteske@freebsd.org writes: >=20 >> How about rquery? What protocol does that use? and what does it talk to? >=20 > It accesses the sqlite database in /var/db/pkg that was previously > retrieved from the remote repository. >=20 This "previously retrieved" has me worried. One of the things that you could do with sysinstall was: 1. Browse packages (nothing else) 2. Exit sysinstall And your system is completely unmodified and the mirror your chose is forgo= tten. Now from what you explained of pkg, I'm worried that for bsdconfig: 1. Browse packages (nothing else) 2. Exit bsdconfig and now because the "pkg rquery" has staged a db, future "pkg" commands are= now influenced. In which case, I think I would best off downloading the sqlite db to a temp= orary location and pointing pkg at it (if that's possible). Because I'm not= sure that I want adhoc browsing in bsdconfig to change the default mirror = (but maybe that's desired? I'm not sure). >> Question: Where can I learn more about the actual format of what's in >> the new tarballs? This is going to be important not for bsdconfig, but >> $work (we have our own build platform; I'm going to have to rewrite it >> from mastering PLIST files to mastering YAML MANIFEST files and I want >> to know all the gritty details). >=20 > You really shouldn't know about the actual format of the tarballs; > your time would be better spent learning the new "pkg create", "pkg > register", and "pkg repo" commands. Depending on your needs, you > might want to write to the libpkg API instead. >=20 That won't work for us. You're not going to like the answer, but it does mean that things like "pkg= create", "pkg register" and "pkg repo" won't work for us. Because FreeBSD packages are just tar-balls, I created a build-system that = allows us to master and re-master them on *any* platform with nothing more = than "make" and a few standard UNIX utilities such as "awk" and etc. This m= akes it extremely convenient for developers and integrators. You can feel f= ree to check out the build tree on Mac OS X, make some changes to a file, c= heck them in, build the package, throw it in the repos, and all from the co= mfort of your own OS. Yes, it flies in the face of "dog-fooding", but the value-add that it bring= s to the table is quite tangible w/respect to our workflow. So the format is still something I want to know quite well. --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you.