Date: Wed, 12 Dec 2018 14:42:00 -0700 From: Gary Aitken <freebsd@dreamchaser.org> To: Polytropon <freebsd@edvax.de>, Paul Schmehl <pschmehl_lists@tx.rr.com> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Forcing port reinstalls without rebuilding over and over again Message-ID: <5116e02a-79e8-d0c5-89c7-88b80effd693@dreamchaser.org> In-Reply-To: <20181212214714.4017e195.freebsd@edvax.de> References: <47758EF2A172AE3BCA2F6E66@Pauls-MacBook-Pro.local> <1793865D5AEE79C2FC27331F@Pauls-MacBook-Pro.local> <20181212204151.659fb436.freebsd@edvax.de> <296D11C4E1B5870932452073@Pauls-MacBook-Pro.local> <20181212214714.4017e195.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/12/18 1:47 PM, Polytropon wrote: > In my opinion, it's a little better to create your own > "top ports list" instead of saving the current state (or > at least have both lists at hand, but only use your own). > In that "top ports list", you list the things you actually > want to use, and you do not care about their depencencies, > simply because portmaster can resolve them on its own. So > first, your list is much more readable (as it will only > contain the software you are interested in, and nothing > of the software you might need to build or run them), and > second, your list will be much more portable and also deal > with the "port not needed, but still installed" problem > described above. That is the way I've done it in the past, using -R -d, and doing so does not rebuild dependencies. I suspect the problem has something to do with -a. Gary
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5116e02a-79e8-d0c5-89c7-88b80effd693>