Date: Mon, 15 Oct 2018 12:16:15 -0400 From: Mike <the.lists@mgm51.com> To: freebsd-questions@freebsd.org Subject: Re: freebsd packages going the debian way! Message-ID: <1a76bc80-9fb6-4731-66e0-1e07c38e8fc0@mgm51.com> In-Reply-To: <20181015160900.767a01052e9642d87f6a3ba0@sohara.org> References: <CAPu-kW-jOpCL93G6YubPaJZQOkTYa5UzrYabdg-WbcbQje8obQ@mail.gmail.com> <049b9e13-688c-39ba-9d77-50e630dc9b6f@kicp.uchicago.edu> <1845546f-470c-4a5f-7118-24cab613e4e0@mgm51.com> <20181015160900.767a01052e9642d87f6a3ba0@sohara.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/15/2018 11:09 AM, Steve O'Hara-Smith wrote: > On Mon, 15 Oct 2018 10:58:53 -0400 > Mike via freebsd-questions <freebsd-questions@freebsd.org> 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. > Thanks for the follow-up. I had been using ports and pkg on the same machine without issues, so I was wondering what the reason was for the warning.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1a76bc80-9fb6-4731-66e0-1e07c38e8fc0>