Date: Fri, 06 Sep 2019 09:41:04 +0100 From: Mike Clarke <jmc-freebsd2@milibyte.co.uk> To: freebsd-questions@freebsd.org Cc: "@lbutlr" <kremels@kreme.com> Subject: Re: Why i need extract not one needed port, but full catalog never needed ports? Message-ID: <11703575.5MqMfjp4zD@curlew> In-Reply-To: <C0664B68-6788-4865-8B1A-FE2E2D813086@kreme.com> References: <1567694626.722400563@f512.i.mail.ru> <20190905182710.9675eb8f.freebsd@edvax.de> <C0664B68-6788-4865-8B1A-FE2E2D813086@kreme.com>
index | next in thread | previous in thread | raw e-mail
On Thursday, 5 September 2019 22:22:20 BST @lbutlr wrote: > AFAIK, there’s no real good way to integrate a pkg install and a ports install. It works quite well if you sync your ports tree against the version used for the current pkg repository. I have a couple of packages which I build from ports because I need different options for one of them and the licensing prevents the distribution of a binary for the other. I have no problems building and installing them when I sync the ports tree against the pkg repository. To sync my ports tree I use a modified copy of https://gist.github.com/reedacartwright/8622973baf89b263a6d7 . Unfortunately the script at github hasn't been updated since 2015 so doesn't have details of package servers for FreeBSD versions later than 10.x but is easy to update if you can find the hostname of the relevant build server, e.g. beefy6.nyi.freebsd.org for 12.0 AMD64. An ideal alternative would be if the package system could have a command which would return the SVN revision of the ports tree used for building the current repository. -- Mike Clarkehelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?11703575.5MqMfjp4zD>