svn commit: r384106 - head/Mk/Uses

[Mathieu Arnold]

+--On 20 avril 2015 23:39:47 -0400 "Philip M. Gollucci"
<pgollucci at p6m7g8.com> wrote:
| If you say so, I have completely different perspective from ruby@,
| apache@, perl@, and to a lesser extent python at .
|
| Like I said I don't  care in the end.  If it works it works.

I don't know for all those teams, but for perl@, there are quite a few
people in it, it's not a one, tired, man band like lua@ was.  If you want
to push for a lua@ team, then ask for a mailing list, and put back the
ports in it, but if the PR assigned to it go stale, it'll be disabanded
again :-)

| On Mon, Apr 20, 2015 at 3:36 PM, John Marino <freebsd.contact at marino.st>
| wrote:
| 
|> On 4/20/2015 21:03, Philip M. Gollucci wrote:
|> > Could you point lua@ to ports@ ?  The goal really is to have a central
|> > place for lua ports (other than ports@).
|> > 
|> > I don't really care one way or the other, I just hate to see large
|> > groups of ports sit a ports@ that need coordination / standards.
|> 
|> I disagree with this suggestion.  In that case, lua maintenance will be
|> hindered by a phantom team.  People tend to avoid team ports because
|> there's always the fear there is some big exp-run brewing (big hidden
|> picture).
|> 
|> lua has a much better chance of being maintained as ports@ in this case,
|> IMO.  There won't be the uncertainty of the unknown / hand-slap.
|> 
|> John



-- 
Mathieu Arnold