Date: Fri, 13 Sep 2024 22:17:38 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 281470] math/py-numpy: Update to 2.1.1 Message-ID: <bug-281470-21822-i7p5pgCVGl@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-281470-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-281470-21822@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D281470 Tomasz "CeDeROM" CEDRO <tomek@cedro.info> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tomek@cedro.info --- Comment #6 from Tomasz "CeDeROM" CEDRO <tomek@cedro.info> --- 1. Will make things backward compatible on existing setups / scripts and wi= ll clearly distinguish new version. Other ports that require version 2 can just update dependencies to py-numpy2 right? 2. Would work like gnupg where security/gnupg is the current version 2 while security/gnupg1 is the old version 1. But it is a bit confusing. 3. There is also third option to use py-numpy1 for version 1, py-numpy2 for version 2,=20 and py-numpy (metaport) for the most recent version. This seems both versat= ile and provides best compatibility no matter what version shows in future. It = will break current setups though. This approach is used for instance with drm-km= od packages (drm-510-kmod for version 5.10, drm-515-kmod for version 5.15, drm-61-kmod for version 6.1, and just drm-kmod metaport for the latest one whatever it is and matches the system requirements). I like this approach m= ost. Only option 1 does not break existing setups. For option 2 or 3 change is o= nly '1` added to the package name to maintain compatibilty. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-281470-21822-i7p5pgCVGl>