[Bug 199571] ports-mgmt/portmaster: [change-request] please ban portmaster

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Tue Apr 21 15:25:46 UTC 2015


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199571

--- Comment #3 from Chris Hutchinson <portmaster at bsdforge.com> ---
(In reply to John Marino from comment #2)
> (In reply to Chris Hutchinson from comment #1)
> > I might also add; it works. So what exactly is your beef, again?
> 
> Maybe in your universe it works.

For it's intended purpose, it works. At least as well as most
"utilitarian" type ports -- it has it's issues, as do the others.

I wish that the OP had combined this with:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199572
it would have made his case here more coherent. This feels
like a rant, after his expressed experience in the other PR.

The other PR looks like an install, as opposed to an upgrade;
which is what ports-mgmt/portmaster's intended use-case is.

> 
> Working ports don't have PR lists like
> this:http://portsmon.freebsd.org/portoverview.py?category=ports-
> mgmt&portname=portmaster&wildcard=
Several of those are dupes, and most are at least a year old.
> 
> 
> This port should be banned.  Now without a _REAL_ maintainer, it's well on
> it's way.
bdrewery@ was maintaining it up to at least 4 weeks ago.
Are you suggesting I maintain this port, that it might get the
attention it needs. Or will that just make me the scourge of the
committers?

IMHO portmaster is a far better choice for upgrades, than
pkg, it you're building from source. It affords you options
*other* than default. Which pkg doesn't cater well to, if at all.

--Chris

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list