Ticket #32495 (closed update: fixed)
mark llvm as replaced_by llvm-2.9
| Reported by: | ryandesign@… | Owned by: | jeremyhu@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | ||
| Port: | clang, llvm, clang-devel, llvm-devel |
Description
llvm 3.0 final was released December 1 so maybe the clang-3.0 and llvm-3.0 ports can be updated to this version. You'll need to increase the ports' epochs when you do this since:
$ ~/scripts/macports/rpm-vercomp 3.0-r143612 3.0 MacPorts considers 3.0-r143612 to be greater than 3.0.
Change History
comment:3 Changed 18 months ago by ryandesign@…
Well, before you can mark the unversioned ports as obsolete (by which I assume you mean replaced_by a versioned one), all ports currently depending on the unversioned ports need to be changed to depend on the versioned ones.
comment:4 Changed 18 months ago by jeremyhu@…
- Port changed from clang-3.0, llvm-3.0 to clang, llvm, clang-devel, llvm-devel
- Summary changed from clang-3.0, llvm-3.0: update to 3.0 final to mark llvm, llvm-devel, clang, clang-devel as replaced_by their versioned port
Yeah, I'll scrub it, but I seem to recall only 1 or 2 that did (and I think at least one was yours).
Also, the 3.0 port was updated to the released version of llvm-3.0 and clang-3.0 probably an hour or so before you filed this ticket
comment:5 Changed 18 months ago by jeremyhu@…
Here's the list of ports which need to be updated still:
ld64 odcctools dragonegg-devel llvm-gcc42 pure py25-llvm py26-llvm py27-llvm
comment:6 Changed 18 months ago by ryandesign@…
I see they were updated to "3.0-r146326" and are still fetching from Subversion. Why not "3.0" and download from the distfile?
comment:7 Changed 18 months ago by jeremyhu@…
Because it makes maintenance easier in case fixes are placed on a branch. If you feel strongly about that, then I can make that change.
comment:8 Changed 18 months ago by ryandesign@…
I would just refer you to this post by Landon. Since a distfile is available, it should be used.
comment:10 Changed 18 months ago by jeremyhu@…
r87893 updates the released versions to use tarballs rather than svn and also sets up the 'port select' support.
comment:12 Changed 18 months ago by mroman@…
port select wont work. also ld64 port is outdated since it depends on llvm port
root ~ port select llvm mp-llvm-3.0 Selecting 'mp-llvm-3.0' for 'llvm' failed: could not create new link "/opt/local/bin/llvmc": target "/opt/local/bin/llvmc-mp-3.0" doesn't exist
comment:13 Changed 18 months ago by jeremyhu@…
comment:15 Changed 17 months ago by jeremyhu@…
- Summary changed from mark llvm, llvm-devel, clang, clang-devel as replaced_by their versioned port to mark llvm as replaced_by llvm-2.9
comment:16 Changed 17 months ago by jeremyhu@…
- Status changed from assigned to closed
- Resolution set to fixed
And now finally done in r88058.
comment:17 Changed 17 months ago by mroman@…
- Status changed from closed to reopened
- Resolution fixed deleted
I suppose it's incorrect:
mr /opt/local/etc/select/clang cat mp-clang-3.0 bin/clang++-mp-3.0 bin/clang-mp-3.0 bin/scan-build-mp-3.0 bin/scan-view-mp-3.0 mr /opt/local/etc/select/clang cat base bin/c-index-test bin/clang++ bin/clang bin/scan-build bin/scan-view
comment:18 Changed 17 months ago by jeremyhu@…
- Status changed from reopened to closed
- Resolution set to fixed
New bugs get new tickets.
comment:19 Changed 17 months ago by jeremyhu@…
r88211 in any event...


yeah, I'm still testing it and the clang_select and llvm_select ports. I expect to push the updated versions today or tomorrow and will send out notice before marking the unversioned ports as obsolete.