Bug 206343 - [patch] upgrade devel/scons to version 2.4.1
Summary: [patch] upgrade devel/scons to version 2.4.1
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
Keywords: patch
Depends on:
Reported: 2016-01-17 22:05 UTC by John Marino
Modified: 2016-02-04 12:29 UTC (History)
1 user (show)

See Also:
linimon: maintainer-feedback? (gavin)

upgrade scons 2.3.0 => 2.4.1 (2.93 KB, patch)
2016-01-17 22:05 UTC, John Marino
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description John Marino freebsd_committer 2016-01-17 22:05:46 UTC
Created attachment 165724 [details]
upgrade scons 2.3.0 => 2.4.1

I ran into an aggravating feature of scons where if process that launches it sets setpid(0,0), it just seizes.  I hoped that upgrading to version 2.4.1 would fix it, but it still happens.  Rather than throw away the work, I'm submitting the patch here.

I'm also wondering if you would prefer to reset maintainership back to ports@FreeBSD.org.  I'm looking at the commit history, and I see you were passed maintainership on 19 Jul 2010.  Since that time, you've been given 8 PRs (7 approved, 1 timed out) but never submitted a PR of your own.  Is that correct?  Usually a maintainer is the one that actively updates the port rather than act as a gatekeeper.
Comment 1 commit-hook freebsd_committer 2016-02-04 12:27:44 UTC
A commit references this bug:

Author: marino
Date: Thu Feb  4 12:27:14 UTC 2016
New revision: 408027
URL: https://svnweb.freebsd.org/changeset/ports/408027

  devel/scons: Upgrade 2.3.0 => 2.4.1 and reset maintainer

  While the maintainer has mostly been responsive since July 2010, his
  actions were limited to approving PRs (mainly to upgrade scons because
  the maintainer wasn't doing it).  Not a single update originated from
  the maintainer himself.  Since being a gatekeeper isn't the purpose of
  a maintainer, I'm going to reset the port on this timeout so that future
  upgrades can get applied faster than they have been.

  PR:		206343
  Submitted by:	myself
  Approved by:	maintainer timeout