Date: Thu, 16 Feb 2017 06:59:10 -0700 (MST) From: Warren Block <wblock@wonkity.com> To: Luca Pizzamiglio <luca.pizzamiglio@gmail.com> Cc: ports@freebsd.org Subject: Re: The future of portmaster Message-ID: <alpine.BSF.2.20.1702160653310.67719@wonkity.com> In-Reply-To: <CAB88xy_RU5TTE=pcsjCWsxWyU-jP91qzD9S-R1v6GKGHJg2=nQ@mail.gmail.com> References: <CAB88xy_RU5TTE=pcsjCWsxWyU-jP91qzD9S-R1v6GKGHJg2=nQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 16 Feb 2017, Luca Pizzamiglio wrote: > Hi all, > > portmaster, a tool used/loved/hated, is almost in abandoned state. > I'm a portmaster user, because, in some cases, it fits my needs. > In other cases, I use other tools, like poudriere or synth, that are > really great. > I don't want to open a discussion here about what it's better, but the > truth is, that I use portmaster and it's not maintained. > So I decided to spend some time to look at it and to work on it. > > I forked it and I start some work. > The plan is: > - remove obsolete features, like the -PP option > - remove pkg_* support (even if someone could be against it), forcing > the usage of pkg > - prepare the support of new features like FLAVORS and subpackages > - adding a new ports, called portmaster-devel, for the new version > > I did a branch on github working of the first two points > (https://github.com/pizzamig/portmaster/tree/remove_oldpkg) > > I'm looking for constructive critics, feedbacks, anything that can > help me to make portmaster an actively maintained and used tool. Thank you for working on this. The most recent commit added my patch to save the command to restart the build when an individual port build fails. It shows "portmaster <flags> ...". Showing the actual flags given would be useful. A less trivial change would be to show the ports to be built in dependency order rather than sorted. Thanks!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1702160653310.67719>