Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 21 Sep 2016 08:40:19 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 212855] Update GOOGLE_CODE to use archive URLs and fix broken ports
Message-ID:  <bug-212855-13-7iOAlN56oH@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-212855-13@https.bugs.freebsd.org/bugzilla/>
References:  <bug-212855-13@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212855

Mathieu Arnold <mat@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|New                         |Closed
         Resolution|---                         |Rejected

--- Comment #2 from Mathieu Arnold <mat@FreeBSD.org> ---
Thank you for your patch.

Before marking all the ports BROKEN, I started by changing the
MASTER_SITE_GOOGLE_CODE entry to make things fetchable again, with the exact
same change you are submitting.
The problem with that approach is that it is just hiding the fact that the
software have not been updated for more than a year and will never be again.
The goal of marking all those ports broken is that people will go and look =
for
where the software went after google code, so that it gets updated when new
releases go out.

If the software has not been moved to some other place, (it takes about 30
seconds to click the automatic migration to github thing, and it is usually
done within the hour,)  since march 2015, it is most likely abandoned and
should not be kept in the ports tree.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-212855-13-7iOAlN56oH>