Date: Thu, 14 Feb 2013 12:53:44 -0700 (MST) From: Warren Block <wblock@wonkity.com> To: awarecons <awarecons@gmail.com> Cc: ports@freebsd.org, Bryan Drewery <bdrewery@FreeBSD.org> Subject: Re: ports-mgmt/portmaster SUGGEST Message-ID: <alpine.BSF.2.00.1302141249360.71109@wonkity.com> In-Reply-To: <CACGq7x0Vs-fdG=0xw7b-ehjeaO_J8u4p6vg3pFXboUFSfRQjcw@mail.gmail.com> References: <CACGq7x0Vs-fdG=0xw7b-ehjeaO_J8u4p6vg3pFXboUFSfRQjcw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 14 Feb 2013, awarecons wrote: > Firstly, thank you for such nice and handy tool. > > Secondly, would suggest you few handy options of portmaster: > > - if port fails give it a second try with question 'Retry?'. A user > may change some influencing options, for e.g. compiler from gcc 4.2 to > 4.6 or clang, before proceeding new try; > > - if port fails give the whole process second try suggesting restart > from the ascend port 'Retry from the ascend port and reconfigure it?', > so the user has opportunity to disable failing sibling. > > Such options are quite handy for large bunches like x11/gnome2|kde4, > when one has 300-500 ports to build and wouldn't oblige to restart the > whole process each time within failure appears. When portmaster fails out, it shows a list of the remaining ports to build. Dependencies that have already been installed will not be rebuilt if you use that list.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1302141249360.71109>