Bug 215305

Summary: lang/clang-devel: out of date and misleading
Product: Ports & Packages Reporter: Matthieu Volat <mazhe>
Component: Individual Port(s)Assignee: Brooks Davis <brooks>
Status: Closed FIXED    
Severity: Affects Some People Flags: bugzilla: maintainer-feedback? (brooks)
Priority: ---    
Version: Latest   
Hardware: Any   
OS: Any   

Description Matthieu Volat 2016-12-14 17:49:30 UTC 
Hi,

For some times, there were lang/clang[...] ports that were (supposedly) metaports accompagning the devel/llvm[...] ports for (I guess?) the purpose of creating a package that would provide clang.

For a while however the llvm port had the CLANG option enabled and especially the lang/clang-devel port stagnated and is now very misleading, dating from a pre-3.8 release (when llvm-devel is around 4.0).

Should not this port be removed?

It seems no other port depends on it:

  /usr/ports# find . -name Makefile | grep clang-devel
  ./lang/clang-devel/Makefile

Thanks
Comment 1 commit-hook freebsd_committer freebsd_triage 2016-12-14 18:38:53 UTC 
A commit references this bug:

Author: brooks
Date: Wed Dec 14 18:38:06 UTC 2016
New revision: 428585
URL: https://svnweb.freebsd.org/changeset/ports/428585

Log:
  Get PORTVERSION from llvm-devel automatically.

  PR:		215305

Changes:
  head/lang/clang-devel/Makefile
Comment 2 Brooks Davis freebsd_committer freebsd_triage 2016-12-14 18:40:00 UTC 
clang-devel was not out of date in practice, but it did have an outdated version number.  It's just there to aid discovery as people expect to be able to install clang by name.  I'd refactored llvm-devel's Makefile.snapshot to support automatic updates quite some time ago, but apparently forgot to finish the job.