From owner-freebsd-current@FreeBSD.ORG Mon Jul 15 07:31:20 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 D84E290F; Mon, 15 Jul 2013 07:31:20 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) by mx1.freebsd.org (Postfix) with ESMTP id 9FFBFD6B; Mon, 15 Jul 2013 07:31:20 +0000 (UTC) Received: from Julian-MBP3.local (124-169-54-70.dyn.iinet.net.au [124.169.54.70]) (authenticated bits=0) by vps1.elischer.org (8.14.5/8.14.5) with ESMTP id r6F7V3IF049997 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 15 Jul 2013 00:31:05 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <51E3A531.6070206@freebsd.org> Date: Mon, 15 Jul 2013 15:30:57 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: Craig Rodrigues Subject: Re: [HEADSUP] No more pkg_install on HEAD by default References: <20130712231637.GS85556@ithaqua.etoilebsd.net> <13CA24D6AB415D428143D44749F57D7201FC2DBD@ltcfiswmsgmb21> <20130713080732.GV85556@ithaqua.etoilebsd.net> <13CA24D6AB415D428143D44749F57D7201FC3AA2@ltcfiswmsgmb21> <13CA24D6AB415D428143D44749F57D7201FC3C92@ltcfiswmsgmb21> <13CA24D6AB415D428143D44749F57D7201FC3FAA@ltcfiswmsgmb21> <1373759460.29471.140661255344697.6A5745F8@webmail.messagingengine.com> <13CA24D6AB415D428143D44749F57D7201FC48D7@ltcfiswmsgmb21> <13CA24D6AB415D428143D44749F57D7201FC4E7E@ltcfiswmsgmb21> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Mark Felder , Devin Teske , "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Mon, 15 Jul 2013 07:31:20 -0000 On 7/15/13 6:43 AM, Craig Rodrigues wrote: > On Sat, Jul 13, 2013 at 10:54 PM, Teske, Devin wrote: > >> >> I assume that poudiere builds packages from ports. >> > Yes. > > >> That's not how we build package repositories here (and would expect that >> there are many more like us). >> > How do you build packages if you are not using FreeBSD ports? Do you have > your own Makefiles which resemble FreeBSD ports, > or are you doing something completely different? > > >> We expect to start with an empty directory, go grab packages that we >> want (one by one) from FTP. Then put those tarballs into a directory. >> There's no additional step because we download the INDEX file to the >> repository too. Local repository is built. >> > What FTP site are you grabbing packages from, the FreeBSD ftp site (or > mirrors) or one of your own? > How are you generating the INDEX file? Do you append to the INDEX file for > every package which you sucessfully download from FTP, > or are you downloading a previously generated INDEX file? What does your > local repository of packages consist of if you are > not using FreeBSD ports? > > >> >> >> But I want bsdconfig to work with local repositories without having >> poudriere. >> >> > You don't have to use poudriere to build a package repository. It is just > an optional tool that > is there for you to try out, and it works quite well when building a package > repository based off of FreeBSD ports. If you don't want to use it, you > don't have to. > > > >> >> I think so too. But right now a *lot* of unanswered questions. >> >> > Possibly, but I think that you are supporting a workflow that people on > this mailing list > don't fully understand. If you could send out a separate e-mail > describing exactly what your workflow is, step-by-step, that might help you > get better answers > to your questions. The FreeBSD ports team has been migrating to pkgng > for the past few years, so a lot of people understand the FreeBSD > ports/packages workflow. > because it has been discussed for a few years on multiple mailing lists, and > at various BSD conferences like BSDCan. What's so difficult to understand? He has a local cache, populated "as needed" from the binary packages released with the FreeBSD release, from the freebsd ftp site.. (He can as a supliment also add versions compiled by himself in the case of security fixes etc. but that isn't required for 99% of the packages. BSDinstall wants dependency information (currently availabele from the INDEX files) to display to the user what he will get) > > Some of the confusion with others on this list is that you are working on > a tool called "bsdconfig" and committing it into FreeBSD-CURRENT, > but the workflow you are trying to support is slightly different than what > the FreeBSD ports/packages teams have been supporting and adapting > their tools and workflow towards. > > I think that if you better describe your workflow in a separate e-mail, > then folks can better recommend how to adapt bsdconfig > to the new pkg tools. You may need to be open to using > things like libpkg inside bsdconfig, if that is the best solution for > bsdconfig inside FreeBSD. > > I agree with you that having a pkgng transition document on the wiki > would be useful for systems integrators. I know that many > people build products based on FreeBSD and leverage the pkg_XXX tools > for building their own products. I have done this myself in the past. > Clarifying the transition path for system integrators would be very helpful. > Maybe you can help write the transition doc, since you have the perspective? > > -- > Craig > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >