Bug 212694

Summary: [maintainer] update lang/ypsilon after google code deprecation
Product: Ports & Packages Reporter: Vitaly Magerya <vmagerya>
Component: Individual Port(s)Assignee: Bartek Rutkowski <robak>
Status: Closed FIXED    
Severity: Affects Only Me CC: robak
Priority: ---    
Version: Latest   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
ypsilon.diff none

Description Vitaly Magerya 2016-09-14 19:11:18 UTC
Created attachment 174789 [details]
ypsilon.diff

Since GOOGLE_CODE is now dead, make lang/ypsilon use Github instead.

Also, make it use GCC, since it segfaults with CLANG (apparently noone uses this port, since I've received zero complaints about this problem).
Comment 1 commit-hook freebsd_committer freebsd_triage 2016-09-15 11:37:22 UTC
A commit references this bug:

Author: robak
Date: Thu Sep 15 11:36:57 UTC 2016
New revision: 422187
URL: https://svnweb.freebsd.org/changeset/ports/422187

Log:
  lang/ypsilon: Update sources and fix builds

  - Remove MASTER_SITES and add USE_GITHUB to fetch sources from new location
  - Add USE_GCC= to fix builds failing with CLANG
  - Add LICENSE and LICENSE_FILE
  - Update pkg-descr

  PR:		212694
  Submitted by:	Vitaly Magerya <vmagerya@gmail.com> (maintainer)

Changes:
  head/lang/ypsilon/Makefile
  head/lang/ypsilon/distinfo
  head/lang/ypsilon/pkg-descr
Comment 2 Bartek Rutkowski freebsd_committer freebsd_triage 2016-09-15 11:37:50 UTC
Committed, thanks!
Comment 3 Vitaly Magerya 2016-09-15 12:19:02 UTC
Hi, Bartek. I see you've added "LICENSE=BSD3CLAUSE", and that's
not really true. Most of Ypsilon is indeed covered by 3-clause BSD
found in license.txt, but it also contains a bunch of libraries
and data files covered by a variety of other licenses: mostly
custom BSD-style licenses with different terms, but also 2-clause
BSD for Unicode data, and there's even a GPL3+ file in the test
suite.

Since our license framework can't express this sort of a mixture,
I suggest LICENSE parts to be removed from the Makefile as
misleading.

(I can file a separate PR about this, if you'd like).