From owner-freebsd-current@FreeBSD.ORG Sun Jul 14 22:43:27 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id CF9D1732; Sun, 14 Jul 2013 22:43:27 +0000 (UTC) (envelope-from crodr001@gmail.com) Received: from mail-lb0-x229.google.com (mail-lb0-x229.google.com [IPv6:2a00:1450:4010:c04::229]) by mx1.freebsd.org (Postfix) with ESMTP id 267B738F; Sun, 14 Jul 2013 22:43:26 +0000 (UTC) Received: by mail-lb0-f169.google.com with SMTP id d10so8928603lbj.14 for ; Sun, 14 Jul 2013 15:43:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=k8R2XgQ+F8d9H8NCZBKD3+oH2kKAmPhE+T7487HOYfY=; b=fpdFhK9y8ZFqsWhJxH7GoSyE5CLYN5xVMHiDrHJpdgIWk7ROcWTQ77cX/4Efi4Zbjx heAy38zUYW/48wJC64i2WvUbjdkoNrjeKgykycYWm1770Bv//DbabCyA3XKHwPjmMUxs mkQvcYrr+jh5C3YJ1bV/jOzkE20r1s93ZPWdAG57WIHHU2tRYD/4ciGWg9Ic8xSfYrhI bykTc6Bxyh9KYx8eAKWRRyc+DFI4RTrSNAZFruP8G5qx95l3aaE/p+KF9263Zgcm8NAb uF0MopZXOvPiQ5961i5njKzvyYVQsdcWcfADNncnB32DdS5YlTG1ELMZmuXUmFxGI+MP bE3g== MIME-Version: 1.0 X-Received: by 10.112.172.35 with SMTP id az3mr22754813lbc.66.1373841805960; Sun, 14 Jul 2013 15:43:25 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.149.38 with HTTP; Sun, 14 Jul 2013 15:43:25 -0700 (PDT) In-Reply-To: <13CA24D6AB415D428143D44749F57D7201FC4E7E@ltcfiswmsgmb21> 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> Date: Sun, 14 Jul 2013 15:43:25 -0700 X-Google-Sender-Auth: w_O8MxWFMBJejyPBvbYR5-oUTsY Message-ID: Subject: Re: [HEADSUP] No more pkg_install on HEAD by default From: Craig Rodrigues To: Devin Teske Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Mark Felder , "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: Sun, 14 Jul 2013 22:43:28 -0000 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. 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