Date: Sat, 18 Nov 2023 16:08:13 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 275167] security/py-service-identity: merge duplicate of security/py-service_identity Message-ID: <bug-275167-7788-CednfIBVLi@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-275167-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-275167-7788@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=3D275167 Palle Girgensohn <girgen@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |girgen@FreeBSD.org --- Comment #4 from Palle Girgensohn <girgen@FreeBSD.org> --- Hej Joakim! Great! I just stumbled on this as well, since pkg-fallout nags me about my = port www/web12ldap, that does not build at all for exactly this reason. May I suggest using the latest port, or at least let the port's name be the same as upstreams. It is named service-identity nowadays. The `_' is replac= ed with `-'. It is also much more popular to use `-' as spacing character in python module names: $ ls -ld */py-*-* | wc -l 1357 $ ls -ld */py-*_* | wc -l=20=20=20=20 66 Albeit, there are ~15 depedant ports for service_identity and just one for service-identity, so I understand the rationale behind the suggest patch. I still think it would be worth to migrate to the same as upstreams. For one thing, the reason for the duplicate is probably just that the name changed upstreams. --=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-275167-7788-CednfIBVLi>