Date: Thu, 17 Dec 2015 10:19:33 +0000 From: Mike Clarke <jmc-freebsd2@milibyte.co.uk> To: freebsd-questions@freebsd.org Subject: Re: Migrating from ports to pkg Message-ID: <20151217101933.3ca571b2@curlew.lan> In-Reply-To: <20151216204758.527efa26316df1e337fb136b@sohara.org> References: <CAPi0psvaKXKo-951QWy7_CEKD4yZO3wK8E=gHKu4=eTAqG%2B4Xg@mail.gmail.com> <5670B7C8.5000603@columbus.rr.com> <56711F73.1020606@FreeBSD.org> <CAPi0psvButCx%2B0J7tQnYog=WDpN3ohsnACc0R_6F0ix=CbRjrg@mail.gmail.com> <20151216204758.527efa26316df1e337fb136b@sohara.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 16 Dec 2015 20:47:58 +0000 Steve O'Hara-Smith <steve@sohara.org> wrote: > When there are only a small number of ports with special options > it's quite easy to just build the essential ports using make missing to get > a list of packages to install before building each port. Just don't forget > to pkg lock all the customised packages so they don't get replaced by > standard ones during an upgrade. This normally works well for me but be aware that if your ports tree isn't in sync with the package repository you can run into dependency problems, I use the sync-ports script from https://gist.github.com/xzhavilla/61dedc55c33cb32c1546 though it needs a little hacking to work on 10.2. The ideal solution would be if there were an option within pkg to update /usr/ports to sync it with the version used for building the current repository or even to just supply the revision number of the ports tree. -- Mike Clarke
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20151217101933.3ca571b2>