[MacPorts] #47775: libint2 @2.0.3 replace previous submission
#47775: libint2 @2.0.3 replace previous submission ---------------------------+-------------------------------- Reporter: yangx59@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: rename libint | Port: libint2 ---------------------------+-------------------------------- Libint2 was submitted several days ago which is named libint. However, because libint and libint2 are not compatible so this could cause some unexpected problems. So here I hope to replace its name libint with libint2. -- Ticket URL: <https://trac.macports.org/ticket/47775> MacPorts <https://www.macports.org/> Ports system for OS X
#47775: libint2 @2.0.3 replace previous submission -------------------------+-------------------------------- Reporter: yangx59@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: libint2 | -------------------------+-------------------------------- Changes (by ryandesign@…): * keywords: rename libint => Comment: Do we then expect to add a libint port later, for libint version 1? Is that needed for anything? We could just as easily keep the existing libint port at version 2, and add a libint1 port if it is ever needed later. -- Ticket URL: <https://trac.macports.org/ticket/47775#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X
#47775: libint2 @2.0.3 replace previous submission -------------------------+-------------------------------- Reporter: yangx59@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: libint2 | -------------------------+-------------------------------- Comment (by yangx59@…): Replying to [comment:1 ryandesign@…]:
Do we then expect to add a libint port later, for libint version 1? Is that needed for anything? We could just as easily keep the existing libint port at version 2, and add a libint1 port if it is ever needed later.
Just in case some package still use the old libint1 version get confused about this libint2 version like CP2K. Is it possible to have 2 version libint port in macport at the same time? -- Ticket URL: <https://trac.macports.org/ticket/47775#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts