Is there a standard procedure for case changes in PORTNAME?Hmm, I'm not a Python expert, but it feels like this line should
For biology/deeptools, upstream changed the name of their wheel file
from "deepTools" to "deeptools" in v4.0.0, which breaks the following
from Uses/python.mk:
PEP517_INSTALL_CMD?=${PYTHON_CMD} -m installer --destdir ${STAGEDIR}
--prefix ${PREFIX} ${BUILD_WRKSRC}/dist/${PORTNAME:C|[-_]+|_|g}-${DISTVERSION}*.whl
On Sep 7, 2026, at 14:22, Jason Bacon <bacon4000@gmail.com> wrote:from "deepTools" to "deeptools" in v4.0.0, which breaks the following =
=20
=20
Is there a standard procedure for case changes in PORTNAME?
=20
For biology/deeptools, upstream changed the name of their wheel file =
=20--prefix ${PREFIX} = ${BUILD_WRKSRC}/dist/${PORTNAME:C|[-_]+|_|g}-${DISTVERSION}*.whl
PEP517_INSTALL_CMD?=3D${PYTHON_CMD} -m installer --destdir ${STAGEDIR} =
=20without adding any hacks to the port, but I'm afraid it will cause "pkg = upgrade" to fail.
Changing PORTNAME from "deepTools" to "deeptools" resolves this =
=20
Thanks,
=20
Jason
=20
--=20
Life is a game. Play hard. Play fair. Have fun.
=20
=20
On Sep 7, 2026, at 15:18, Charlie Li <vishwin@freebsd.org> wrote:from "deepTools" to "deeptools" in v4.0.0, which breaks the following =
=20
Moin Rahman wrote:
On Sep 7, 2026, at 14:22, Jason Bacon <bacon4000@gmail.com> wrote:
Is there a standard procedure for case changes in PORTNAME?
=20
For biology/deeptools, upstream changed the name of their wheel file =
${STAGEDIR} --prefix ${PREFIX} = ${BUILD_WRKSRC}/dist/${PORTNAME:C|[-_]+|_|g}-${DISTVERSION}*.whl=20
PEP517_INSTALL_CMD?=3D${PYTHON_CMD} -m installer --destdir =
without adding any hacks to the port, but I'm afraid it will cause "pkg = upgrade" to fail.=20
Changing PORTNAME from "deepTools" to "deeptools" resolves this =
normalisation goes. The project decided to pre-normalise their name in = metadata "to avoid warning emails after upload of wheels", [0] which is =`deeptools` and `deepTools` are equivalent as far as Python name ==20The PORTNAME should always be the project name in PYPI.
Distfiles can have different naming specially the source dist.
Keep PORTNAME consistent with PYPI projects althought there
has been incidents where upstreams also renamed PYPI projects.
Change only the DISTNAME to match the release file name.
=20case.
For ports purposes, there's not really a wrong way to go about this =
=20https://github.com/deeptools/deepTools/pull/1452/changes/7d34958a912bb65cf= 75ae0b0eae5b1a1473bccb4
[0] =
=20
--=20
Charlie Li
...nope, still don't have an exit line.
On Mon, Sep 7, 2026 at 3:40rC>PM Jason Bacon <bacon4000@gmail.com> wrote:
Is there a standard procedure for case changes in PORTNAME?
For biology/deeptools, upstream changed the name of their wheel file
from "deepTools" to "deeptools" in v4.0.0, which breaks the following
from Uses/python.mk:
PEP517_INSTALL_CMD?=${PYTHON_CMD} -m installer --destdir ${STAGEDIR}
--prefix ${PREFIX}
${BUILD_WRKSRC}/dist/${PORTNAME:C|[-_]+|_|g}-${DISTVERSION}*.whl
Hmm, I'm not a Python expert, but it feels like this line should
reference ${DISTNAME} instead.
Moin Rahman wrote:
They fixed their typo immediately after: https://github.com/deeptools/ deepTools/pull/1452/changes/19effc5633f90ec37c3b3f9fde8a7252ee9ebab6
On Sep 7, 2026, at 15:18, Charlie Li <vishwin@freebsd.org> wrote:I have no clue like how cow deepTools normalizes to deepools.
Moin Rahman wrote:
`deeptools` and `deepTools` are equivalent as far as Python nameOn Sep 7, 2026, at 14:22, Jason Bacon <bacon4000@gmail.com> wrote:The PORTNAME should always be the project name in PYPI.
Is there a standard procedure for case changes in PORTNAME?
For biology/deeptools, upstream changed the name of their wheel
file from "deepTools" to "deeptools" in v4.0.0, which breaks the
following from Uses/python.mk:
PEP517_INSTALL_CMD?=${PYTHON_CMD} -m installer --destdir
${STAGEDIR} --prefix ${PREFIX} ${BUILD_WRKSRC}/dist/${PORTNAME:C|[- >>>>> _]+|_|g}-${DISTVERSION}*.whl
Changing PORTNAME from "deepTools" to "deeptools" resolves this
without adding any hacks to the port, but I'm afraid it will cause
"pkg upgrade" to fail.
Distfiles can have different naming specially the source dist.
Keep PORTNAME consistent with PYPI projects althought there
has been incidents where upstreams also renamed PYPI projects.
Change only the DISTNAME to match the release file name.
normalisation goes. The project decided to pre-normalise their name
in metadata "to avoid warning emails after upload of wheels", [0]
which is what now appears in PyPI, but it appears still otherwise
marketed as `deepTools`.
For ports purposes, there's not really a wrong way to go about this
case.
[0] https://github.com/deeptools/deepTools/pull/1452/
changes/7d34958a912bb65cf75ae0b0eae5b1a1473bccb4
That is one character less, isn't it?
These and the other almost 400 commits got squashed or fixed-up into a single commit anyway.
On Sep 7, 2026, at 15:18, Charlie Li <vishwin@freebsd.org> wrote:
Moin Rahman wrote:
`deeptools` and `deepTools` are equivalent as far as Python name normalisation goes. The project decided to pre-normalise their name in metadata "to avoid warning emails after upload of wheels", [0] which is what now appears in PyPI, but it appears still otherwise marketed as `deepTools`.On Sep 7, 2026, at 14:22, Jason Bacon <bacon4000@gmail.com> wrote:The PORTNAME should always be the project name in PYPI.
Is there a standard procedure for case changes in PORTNAME?
For biology/deeptools, upstream changed the name of their wheel file from "deepTools" to "deeptools" in v4.0.0, which breaks the following from Uses/python.mk:
PEP517_INSTALL_CMD?=${PYTHON_CMD} -m installer --destdir ${STAGEDIR} --prefix ${PREFIX} ${BUILD_WRKSRC}/dist/${PORTNAME:C|[-_]+|_|g}-${DISTVERSION}*.whl
Changing PORTNAME from "deepTools" to "deeptools" resolves this without adding any hacks to the port, but I'm afraid it will cause "pkg upgrade" to fail.
Distfiles can have different naming specially the source dist.
Keep PORTNAME consistent with PYPI projects althought there
has been incidents where upstreams also renamed PYPI projects.
Change only the DISTNAME to match the release file name.
For ports purposes, there's not really a wrong way to go about this case.
[0] https://github.com/deeptools/deepTools/pull/1452/changes/7d34958a912bb65cf75ae0b0eae5b1a1473bccb4
--
Charlie Li
...nope, still don't have an exit line.
I have no clue like how cow deepTools normalizes to deepools.
That is one character less, isn't it?
Kind regards,
Moin
On 9/7/26 08:23, Moin Rahman wrote:
On Sep 7, 2026, at 15:18, Charlie Li <vishwin@freebsd.org> wrote:
Moin Rahman wrote:
`deeptools` and `deepTools` are equivalent as far as Python nameOn Sep 7, 2026, at 14:22, Jason Bacon <bacon4000@gmail.com> wrote:The PORTNAME should always be the project name in PYPI.
Is there a standard procedure for case changes in PORTNAME?
For biology/deeptools, upstream changed the name of their wheel
file from "deepTools" to "deeptools" in v4.0.0, which breaks the
following from Uses/python.mk:
PEP517_INSTALL_CMD?=${PYTHON_CMD} -m installer --destdir
${STAGEDIR} --prefix ${PREFIX} ${BUILD_WRKSRC}/dist/${PORTNAME:C|[- >>>>> _]+|_|g}-${DISTVERSION}*.whl
Changing PORTNAME from "deepTools" to "deeptools" resolves this
without adding any hacks to the port, but I'm afraid it will cause
"pkg upgrade" to fail.
Distfiles can have different naming specially the source dist.
Keep PORTNAME consistent with PYPI projects althought there
has been incidents where upstreams also renamed PYPI projects.
Change only the DISTNAME to match the release file name.
normalisation goes. The project decided to pre-normalise their name
in metadata "to avoid warning emails after upload of wheels", [0]
which is what now appears in PyPI, but it appears still otherwise
marketed as `deepTools`.
For ports purposes, there's not really a wrong way to go about this
case.
[0] https://github.com/deeptools/deepTools/pull/1452/
changes/7d34958a912bb65cf75ae0b0eae5b1a1473bccb4
--
Charlie Li
...nope, still don't have an exit line.
I have no clue like how cow deepTools normalizes to deepools.
That is one character less, isn't it?
Kind regards,
Moin
Another nice catch.-a Looks like they substituted one bug for another.
I'll talk to upstream.
On 9/7/26 08:44, Jason Bacon wrote:
On 9/7/26 08:23, Moin Rahman wrote:
On Sep 7, 2026, at 15:18, Charlie Li <vishwin@freebsd.org> wrote:
Moin Rahman wrote:
`deeptools` and `deepTools` are equivalent as far as Python nameOn Sep 7, 2026, at 14:22, Jason Bacon <bacon4000@gmail.com> wrote: >>>>>> Is there a standard procedure for case changes in PORTNAME?The PORTNAME should always be the project name in PYPI.
For biology/deeptools, upstream changed the name of their wheel
file from "deepTools" to "deeptools" in v4.0.0, which breaks the
following from Uses/python.mk:
PEP517_INSTALL_CMD?=${PYTHON_CMD} -m installer --destdir
${STAGEDIR} --prefix ${PREFIX} ${BUILD_WRKSRC}/dist/${PORTNAME:C| >>>>>> [- _]+|_|g}-${DISTVERSION}*.whl
Changing PORTNAME from "deepTools" to "deeptools" resolves this
without adding any hacks to the port, but I'm afraid it will cause >>>>>> "pkg upgrade" to fail.
Distfiles can have different naming specially the source dist.
Keep PORTNAME consistent with PYPI projects althought there
has been incidents where upstreams also renamed PYPI projects.
Change only the DISTNAME to match the release file name.
normalisation goes. The project decided to pre-normalise their name
in metadata "to avoid warning emails after upload of wheels", [0]
which is what now appears in PyPI, but it appears still otherwise
marketed as `deepTools`.
For ports purposes, there's not really a wrong way to go about this
case.
[0] https://github.com/deeptools/deepTools/pull/1452/
changes/7d34958a912bb65cf75ae0b0eae5b1a1473bccb4
--
Charlie Li
...nope, still don't have an exit line.
I have no clue like how cow deepTools normalizes to deepools.
That is one character less, isn't it?
Kind regards,
Moin
Another nice catch.-a Looks like they substituted one bug for another.
I'll talk to upstream.
Nevermind, already fixed.
i-y+<|eUe'u\c+-Ue]o{ j+#k&!Ut yoOou4y+2y-j|o-ee%~Vaz|hY2bo{ |-hY%,i+oRkLu--- Synchronet 3.22a-Linux NewsLink 1.2
On Sep 7, 2026, at 14:22, Jason Bacon <bacon4000@gmail.com> wrote:
Is there a standard procedure for case changes in PORTNAME?
For biology/deeptools, upstream changed the name of their wheel file from "deepTools" to "deeptools" in v4.0.0, which breaks the following from Uses/python.mk:
PEP517_INSTALL_CMD?=${PYTHON_CMD} -m installer --destdir ${STAGEDIR} --prefix ${PREFIX} ${BUILD_WRKSRC}/dist/${PORTNAME:C|[-_]+|_|g}-${DISTVERSION}*.whl
Changing PORTNAME from "deepTools" to "deeptools" resolves this without adding any hacks to the port, but I'm afraid it will cause "pkg upgrade" to fail.
Thanks,
Jason
--
Life is a game. Play hard. Play fair. Have fun.
The PORTNAME should always be the project name in PYPI.
Distfiles can have different naming specially the source dist.
Keep PORTNAME consistent with PYPI projects althought there
has been incidents where upstreams also renamed PYPI projects.
Change only the DISTNAME to match the release file name.
Kind regards,
Moin
On Sep 8, 2026, at 23:07, Jason Bacon <bacon4000@gmail.com> wrote:from "deepTools" to "deeptools" in v4.0.0, which breaks the following =
=20
On 9/7/26 08:02, Moin Rahman wrote:
On Sep 7, 2026, at 14:22, Jason Bacon <bacon4000@gmail.com> wrote:
=20
=20
Is there a standard procedure for case changes in PORTNAME?
=20
For biology/deeptools, upstream changed the name of their wheel file =
${STAGEDIR} --prefix ${PREFIX} = ${BUILD_WRKSRC}/dist/${PORTNAME:C|[-_]+|_|g}-${DISTVERSION}*.whl=20
PEP517_INSTALL_CMD?=3D${PYTHON_CMD} -m installer --destdir =
without adding any hacks to the port, but I'm afraid it will cause "pkg = upgrade" to fail.=20
Changing PORTNAME from "deepTools" to "deeptools" resolves this =
handbook. I'm not finding anything about it there now.=20=20The PORTNAME should always be the project name in PYPI.
Thanks,
=20
Jason
=20
--=20
Life is a game. Play hard. Play fair. Have fun.
=20
=20
Distfiles can have different naming specially the source dist.
Keep PORTNAME consistent with PYPI projects althought there
has been incidents where upstreams also renamed PYPI projects.
Change only the DISTNAME to match the release file name.
Kind regards,
Moin
Is this policy? If so, we should document it in the porter's =
=20
Best,
=20
Jason
=20
--=20
Life is a game. Play hard. Play fair. Have fun.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 74 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 35:26:47 |
| Calls: | 1,196 |
| Calls today: | 1 |
| Files: | 1,354 |
| D/L today: |
16 files (19,622K bytes) |
| Messages: | 294,770 |