New port with maintainer [was: Question about maintainers]

Paul Schmehl pauls at
Thu Jul 28 21:07:28 GMT 2005

--On Thursday, July 28, 2005 13:48:07 -0700 Frank Mayhar <frank at> 
> Let's look at what I wrote in my "last paragraph."  I said:
> 	I _certainly_ think that a port submitted with a maintainer of
> 	'ports at' should hit the bit bucket immediately and
> 	never see the light of day.  If it's important enough to submit,
> 	it should be important enough to maintain.
> Now correct me if I'm wrong, but tcl, itcl, tk and iwidgets were already
> in ports, were they not?  So they could not possibly have been "submitted
> with a maintainer of 'ports at'"  Of course, this is not to say
> that you should not have been the stuckee for those ports.  If you
> learned enough to update them, you probably learned enough to continue to
> maintain them.  (You may not have had the _time_ to maintain them, but
> that's an entirely different issue.)
> Quite honestly, if you were to feel intimidated, that's _your_ problem.
> If you feel too intimidated to take something on, then don't do so, but
> also don't complain that it hasn't been addressed.
I'm not sure why you're being so obtuse.  I am not complaining.  I'm simply 
saying that if we no longer allow ports with a maintainer of ports, there 
are problems that will arise that need to be thought through.

Obviously, if I *really* felt intimidated, I wouldn't be submitting the 
ports, would I?  But not everyone is quite as ambitious as I am, and some 
might actually not bother to ever submit a port if they had to create or 
fix others to get theirs working.  If the goal is to have working ports for 
the community, then ISTM that there should not be rules in place that 
*discourage* new port submitters from even trying.
> Believe me, that situation would have been preferable the content of this
> thread.  As far as the package itself is concerned, I honestly don't
> care.   If I _did_ care, though, I would do something about it, either
> privately or in public, and I would do my damnedest to adhere to
> professional standards.  I wouldn't whine about how doing it right is too
> "intimidating."
I wasn't whining.  You should have recognized that.
> Ultimately, this is a tempest in a teapot.  If you can't maintain those
> ports, you can't, and no amount of browbeating is going to change that.
> On the other hand, don't expect the FreeBSD folks to change their policy
> just to make you feel better.

Gee, and here I thought we were actually trying to *encourage* people to 
adopt ports.  Silly me.

Paul Schmehl (pauls at
Adjunct Information Security Officer
University of Texas at Dallas
AVIEN Founding Member

More information about the freebsd-ports mailing list