From owner-freebsd-questions@FreeBSD.ORG Wed Sep 17 07:22:57 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1DB09270 for ; Wed, 17 Sep 2014 07:22:57 +0000 (UTC) Received: from blue.qeng-ho.org (blue.qeng-ho.org [217.155.128.241]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A39222A6 for ; Wed, 17 Sep 2014 07:22:56 +0000 (UTC) Received: from arthur.home.qeng-ho.org (arthur.home.qeng-ho.org [172.23.1.2]) by fileserver.home.qeng-ho.org (8.14.7/8.14.5) with ESMTP id s8H7MjdB028834; Wed, 17 Sep 2014 08:22:47 +0100 (BST) (envelope-from freebsd@qeng-ho.org) Message-ID: <541936C5.3080601@qeng-ho.org> Date: Wed, 17 Sep 2014 08:22:45 +0100 From: Arthur Chance User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: =?UTF-8?B?UmFkZWsgS3JlasSNYQ==?= , "'Warren Block'" , "'William A. Mahaffey III'" Subject: Re: A lot of pkg problems References: <2509308.9rytrV7MvD@penguin> <5411A89B.4010707@gmail.com> <1812950.bWcWxrzvJI@penguin> <54189CD1.7070102@webrz.net> <5418A5EE.1030304@hiwaay.net> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Cc: "'freebsd-questions@freebsd.org'" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Sep 2014 07:22:57 -0000 On 16/09/2014 22:33, Radek Krejča wrote: >> The amount of time people are willing to invest in "saving time" with >> packages is interesting. In many cases, they could have built from >> ports and been done quicker overall, or at least with less user >> involvement. > > Chmm. I like packages, because of saving time and should be safe for using > on production servers - thats my idea. But now I am not able to use it, > because a lot of packages are not working, as on the top of this thread > described. > > And this is complication for me - I rely on packages on production servers, > where saving time is very important. Yes, I can create own repository and > manage own packages but I like this idea. But this idea is not working for > some weeks. Unhappy situation. Using poudriere to build your own repo is *very* easy and lets you build only the packages you need (so is quicker than waiting the four-ish days that the main repository takes to build everything), with the options you want. It will probably take a day or two at most, depending on how many packages you need, which has to be better than "not working for weeks".