Updating curl

[Jerry]

On Sun, 24 Mar 2013 13:10:25 +0100
olli hauer articulated:

[snip}

> Just a quick question.
> How many ports do you maintain?

Three, very simple ports.
 
> I have to ask this question because it looks like you are always
> coming up with the same copy pasted text snippets (do you have them
> as text blocks in vim or emacs?)

I have never created a boilerplate if that is what you are referring to.
 
> If you are willing to do the maintenance of an actual curl port please
> come up with an patch and request maintainer ship.

I am actually thinking about updating curl on my system and no I would
not release it since I am (1) not the maintain of said port, and (2) I
don't have the time to actively maintain it. Which brings us back to my
original statement, that being that if the current maintainer is not
going to properly maintain the port than they should publicly state
that fact which would allow another individual with sufficient time and
skill to do so.

If you remember a few months ago, there was a discussion as to why
"Bash" lingered on for months, actually a year, with numerous patches
being issued by the Bash author yet never being included in the port's
system. Finally, another user created a "devel" port. Perhaps that is
the proper way to handle this problem. "Postfix", probably the best
maintained port in the entire system. has both a "stable" release and a
"current" release in the ports system. I will agree that
"sahil at FreeBSD.org" is probably an over achiever, but it is an example
of what can be accomplished, and in virtual real time no less, when
someone dedicates themselves to a task.

-- 
Jerry ♔

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__________________________________________________________________