From owner-freebsd-questions@freebsd.org Mon Oct 15 15:09:21 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9855E10DDF22 for ; Mon, 15 Oct 2018 15:09:21 +0000 (UTC) (envelope-from 4250.10.freebsd-questions=freebsd.org@email-od.com) Received: from s1-b0c6.socketlabs.email-od.com (s1-b0c6.socketlabs.email-od.com [142.0.176.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 463B377C72 for ; Mon, 15 Oct 2018 15:09:21 +0000 (UTC) (envelope-from 4250.10.freebsd-questions=freebsd.org@email-od.com) DKIM-Signature: v=1; a=rsa-sha256; d=email-od.com;i=@email-od.com;s=dkim; c=relaxed/relaxed; q=dns/txt; t=1539616161; x=1542208161; h=content-transfer-encoding:content-type:mime-version:references:in-reply-to:message-id:subject:cc:to:from:date:x-thread-info; bh=OCMJD58HRhAUsZZNj7pRPI069ZyJn+SirTi4mCkqmtA=; b=U5/9ZI46Q9DkglsYOD01+YlMh5R46qi7xYoWfDfw0mo7GZ1rx781N08eXRL5/V36kVLKWRvChZNz6ovdviLFW9pNI1z0kiEwItPbK3fEftbwCF/2g1q5b3kaxkw5l2dhJWMTkxhM8DJNjf/sUpMJeJclnP6PYUIDKxroRCIVS1s= X-Thread-Info: NDI1MC4xMi4xOWQwMDAwMDA1NTA1NTguZnJlZWJzZC1xdWVzdGlvbnM9ZnJlZWJzZC5vcmc= Received: from r4.us-west-2a.aws.in.socketlabs.com (r4.us-west-2a.aws.in.socketlabs.com [54.149.236.199]) by mxsg2.email-od.com with ESMTP(version=Tls12 cipher=Aes256 bits=256); Mon, 15 Oct 2018 11:09:04 -0400 Received: from smtp.lan.sohara.org (EMTPY [89.127.62.20]) by r4.us-west-2a.aws.in.socketlabs.com with ESMTP(version=Tls12 cipher=Aes256 bits=256); Mon, 15 Oct 2018 11:09:03 -0400 Received: from [192.168.63.1] (helo=steve.lan.sohara.org) by smtp.lan.sohara.org with smtp (Exim 4.91 (FreeBSD)) (envelope-from ) id 1gC4UO-0005n6-Ch; Mon, 15 Oct 2018 16:09:00 +0100 Date: Mon, 15 Oct 2018 16:09:00 +0100 From: Steve O'Hara-Smith To: freebsd-questions@freebsd.org Cc: Mike Subject: Re: freebsd packages going the debian way! Message-Id: <20181015160900.767a01052e9642d87f6a3ba0@sohara.org> In-Reply-To: <1845546f-470c-4a5f-7118-24cab613e4e0@mgm51.com> References: <049b9e13-688c-39ba-9d77-50e630dc9b6f@kicp.uchicago.edu> <1845546f-470c-4a5f-7118-24cab613e4e0@mgm51.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.1) X-Clacks-Overhead: "GNU Terry Pratchett" Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Oct 2018 15:09:21 -0000 On Mon, 15 Oct 2018 10:58:53 -0400 Mike via freebsd-questions wrote: > What is the reason for not using ports and pkg on the same machine? There are a number of difficulties: 1: Making sure that your ports tree is in sync with the one used for package building. 2: Preventing pkg from replacing your ports during pkg upgrade (careful use of pkg lock is required) 3: Dependencies built with different options may not always work. I've found it fairly easy to handle a few leaf packages as ports more than that is likely to get fiddly. -- Steve O'Hara-Smith