Summary: | [PATCH] update for stunnel | ||||||
---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | martti.kuparinen <martti.kuparinen> | ||||
Component: | Individual Port(s) | Assignee: | Peter Pentchev <roam> | ||||
Status: | Closed FIXED | ||||||
Severity: | Affects Only Me | ||||||
Priority: | Normal | ||||||
Version: | Latest | ||||||
Hardware: | Any | ||||||
OS: | Any | ||||||
Attachments: |
|
Description
martti.kuparinen
2001-10-31 10:20:00 UTC
On Wed, Oct 31, 2001 at 08:01:06AM -0800, roam@FreeBSD.org wrote: > Synopsis: [PATCH] update for stunnel > > State-Changed-From-To: open->feedback > State-Changed-By: roam > State-Changed-When: Wed Oct 31 07:59:18 PST 2001 > State-Changed-Why: > Is there a reason for this port to USE_AUTOCONF? > I tried changing it to GNU_CONFIGURE=yes, and everything worked > just fine. I see that GNU_CONFIGURE was changed to USE_AUTOCONF > as part of your update to version 3.8.4, submitted in PR ports/19637; > what was the reason for this change? > > Other than that, this update is trivial and ready to be committed. Maybe I should explain a bit more what I mean by 'everything worked just fine' - the MD5 checksum of the stunnel executable did not change :) G'luck, Peter -- This sentence would be seven words long if it were six words shorter. State Changed From-To: open->feedback Is there a reason for this port to USE_AUTOCONF? I tried changing it to GNU_CONFIGURE=yes, and everything worked just fine. I see that GNU_CONFIGURE was changed to USE_AUTOCONF as part of your update to version 3.8.4, submitted in PR ports/19637; what was the reason for this change? Other than that, this update is trivial and ready to be committed. Responsible Changed From-To: freebsd-ports->roam I'll take care of this. State Changed From-To: feedback->closed Update committed, thanks! |