Opened 10 years ago
Closed 10 years ago
#44995 closed update (fixed)
gcc410: rename to gcc5
Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | mww@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | cooljeanius (Eric Gallager) | |
Port: | gcc410 gcc5 |
Description
Following the new gcc version numbering announcement, the gcc410 port will need to be renamed gcc5 to continue with updates. A stub gcc410 port should be left for one year marked as replaced_by gcc5
to help existing users of gcc410 upgrade cleanly.
I created the initial gcc410 port (from your gcc49 port), and if you like I can work on this renaming situation as well.
Change History (5)
comment:1 follow-up: 2 Changed 10 years ago by larryv (Lawrence Velázquez)
comment:2 Changed 10 years ago by seanfarley (Sean Farley)
Replying to larryv@…:
I was actually thinking about renaming all the GCC ports to “
gcc-X.Y
” for consistency with the Clang ports. I haven’t fleshed out the details yet; the main sticking point is the fact that base currently expects the current “gccXY
” format when selecting compilers. I’m not quite sure how to deal with that.
+1
comment:3 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Let's discuss that on the macports-dev mailing list first. This ticket is just about updating this one port.
comment:5 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | new → closed |
I was actually thinking about renaming all the GCC ports to “
gcc-X.Y
” for consistency with the Clang ports. I haven’t fleshed out the details yet; the main sticking point is the fact that base currently expects the current “gccXY
” format when selecting compilers. I’m not quite sure how to deal with that.