summaryrefslogtreecommitdiff
path: root/dev-cpp/pystring
AgeCommit message (Collapse)Author
2025-07-14dev-cpp/pystring: Stabilize 1.1.4-r2 x86, #960177Arthur Zamarin
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
2025-07-14dev-cpp/pystring: Stabilize 1.1.4-r2 amd64, #960177Arthur Zamarin
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
2025-05-26dev-cpp/pystring: Fix compliation with cmake 4Sebastian Parborg
Closes: https://bugs.gentoo.org/952037 Signed-off-by: Sebastian Parborg <sebastian@blender.org> Part-of: https://github.com/gentoo/gentoo/pull/42213 Closes: https://github.com/gentoo/gentoo/pull/42213 Signed-off-by: Sam James <sam@gentoo.org>
2025-05-20dev-cpp/pystring: drop 1.1.3-r1Andreas Sturmlechner
Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org>
2025-03-10dev-cpp/pystring: force rebuild and bump subslot for broken 1.1.4 releaseEli Schwartz
``` * CMP: =dev-cpp/pystring-1.1.3-r1 with dev-cpp/pystring-1.1.4/image * FILES:-usr/lib64/libpystring.so.0.0 * FILES:+usr/lib64/libpystring.so (-rwxr-xr-x root:root) * SONAME:-libpystring.so.0.0(64) * SONAME:+libpystring.so(64) ``` This breaks binpackage usage. preserved-libs sort of saves you, maybe, if you built locally. Reverse dependencies are linked to .so.0.0, but the new package only contains .so -- technically, if the reverse were true, linked binaries would still work if you squint, but in the current state this simply does not work at all. The background here is weird. Upstream has a Makefile, which calls the system libtool (broken!) and produces a soname of .so.0 in the event that it succeeds at producing a library. We patched in an unofficial cmake build (???) that set the soname to .so.0.0 instead, which isn't very libtool of them but whatever. Upstream didn't actually accept that, they wrote their own which is "simpler" and set the soname to .so. Now we have 3 different sonames in use, but one of them was only in use in *Gentoo* for a couple of days, unstable, back in 2021. As standard, we solve changing sonames by bumping subslot to force a rebuild. Straight to stable it goes, with a revbump since people already have it installed and now have broken binaries. Bug: https://github.com/gentoo/gentoo/pull/21209 Bug: https://github.com/gentoo/gentoo/pull/39761 Bug: https://github.com/imageworks/pystring/pull/29 Fixes: 91773fd1eb57d4c080c0151f5899f1631ddf2aac Fixes: 4b6bedcedfc6a2e7b8c59262dea3d3e42f248427 Signed-off-by: Eli Schwartz <eschwartz@gentoo.org>
2025-03-08dev-cpp/pystring: Stabilize 1.1.4 amd64, #950894Arthur Zamarin
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
2025-03-08dev-cpp/pystring: Stabilize 1.1.4 x86, #950894Arthur Zamarin
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
2024-12-22dev-cpp/pystring: drop libtool BDEPENDSam James
We should have dropped this in 91773fd1eb57d4c080c0151f5899f1631ddf2aac when we switched to CMake. Signed-off-by: Sam James <sam@gentoo.org>
2024-12-22dev-cpp/pystring: Bump to 1.1.4Sebastian Parborg
Closes: https://bugs.gentoo.org/943179 Signed-off-by: Sebastian Parborg <darkdefende@gmail.com> Closes: https://github.com/gentoo/gentoo/pull/39761 Signed-off-by: Sam James <sam@gentoo.org>
2024-01-15Move {sys-devel → dev-build}/libtoolMichał Górny
Signed-off-by: Michał Górny <mgorny@gentoo.org> Closes: https://github.com/gentoo/gentoo/pull/34807 Signed-off-by: Michał Górny <mgorny@gentoo.org>
2023-08-01dev-cpp/pystring: drop unnecessary RESTRICT=mirror, cleanup BDEPENDSam James
Signed-off-by: Sam James <sam@gentoo.org>
2022-02-28dev-cpp/pystring: Stabilize 1.1.3-r1 x86, #833158Sam James
Signed-off-by: Sam James <sam@gentoo.org>
2022-02-28dev-cpp/pystring: keyword 1.1.3-r1 for ~riscvAlex Fan
Signed-off-by: Alex Fan <alex.fan.q@gmail.com> Signed-off-by: Yixun Lan <dlan@gentoo.org>
2021-10-31dev-cpp/pystring: Stabilize 1.1.3-r1 amd64, #803884Sam James
Signed-off-by: Sam James <sam@gentoo.org>
2021-09-19dev-cpp/pystring: Keyword 1.1.3-r1 ppc64, #795279Sam James
Signed-off-by: Sam James <sam@gentoo.org>
2021-09-19dev-cpp/pystring: Keyword 1.1.3-r1 x86, #795279Sam James
Signed-off-by: Sam James <sam@gentoo.org>
2021-09-19dev-cpp/pystring: Keyword 1.1.3-r1 arm, #795279Sam James
Signed-off-by: Sam James <sam@gentoo.org>
2021-09-19dev-cpp/pystring: Keyword 1.1.3-r1 arm64, #795279Sam James
Signed-off-by: Sam James <sam@gentoo.org>
2021-09-11**/metadata.xml: Replace http by https in DOCTYPE elementUlrich Müller
Bug: https://bugs.gentoo.org/552720 Signed-off-by: Ulrich Müller <ulm@gentoo.org>
2021-06-12dev-cpp/pystring: Don't use hardcoded g++ (convert to CMake)Sebastian Parborg
Convert the project into cmake so we get compiler switching for free. Closes: https://bugs.gentoo.org/795156 Closes: https://bugs.gentoo.org/795168 Signed-off-by: Sebastian Parborg <darkdefende@gmail.com> Closes: https://github.com/gentoo/gentoo/pull/21209 Signed-off-by: Sam James <sam@gentoo.org>
2021-06-10dev-cpp/pystring: fix licence to be BSDSam James
Closes: https://bugs.gentoo.org/795297 Reported-by: Alessandro Barbieri <lssndrbarbieri@gmail.com> Signed-off-by: Sam James <sam@gentoo.org>
2021-06-10dev-cpp/pystring: New packageSebastian Parborg
Pystring is a collection of C++ functions which match the interface and behavior of python's string class methods using std::string. Implemented in C++, it does not require or make use of a python interpreter. It provides convenience and familiarity for common string operations not included in the standard C++ library. It's also useful in environments where both C++ and python are used. Signed-off-by: Sebastian Parborg <darkdefende@gmail.com> Signed-off-by: Sam James <sam@gentoo.org>