as per the coding style guide:
https://projects.gentoo.org/qa/policy-guide/ebuild-format.html#pg0101
only these changes were done:
[ -e ... ] to [[ -e ... ]]
[ -z ... ] to [[ -z ... ]]
[ -n ... ] to [[ -n ... ]]
[ ! -f ... ] to [[ ! -f ... ]]
[ -f ... ] to [[ -f ... ]]
[ -d ... ] to [[ -d ... ]]
the changes were generated using this command:
```
find -name '*.ebuild' -exec sed -i -E \
's|([^[])\[+(\s+)([^]]+)(\s+)\]+([^]]\|$)|\1\[\[\2\3\4\]\]\5|g' \
{} \+
```
this is aimed to be a series of commits meant to replace all instance of
POSIX [ ... ] to bash's [[ ... ]], to make guru up to date with the
coding style guide.
this process is divided up into a series of commits in order to make
review and testing more easy
Signed-off-by: ingenarel (NeoJesus) <ingenarel_neojesus@disroot.org>
Part-of: https://codeberg.org/gentoo/guru/pulls/6
Signed-off-by: Michał Górny <mgorny@gentoo.org>
as per the coding style guide:
https://projects.gentoo.org/qa/policy-guide/ebuild-format.html#pg0101
if it previously used [ ${PV} ... ] it uses [[ ${PV} ... ]] now
if it previously used [[ ${PV} = b ]] or [ ${PV} = b ], it uses
[[ ${PV} == b ]] now
the changes were generated using these two commands:
```
find -name '*.ebuild' -exec sed -i -E \
's|([^[])\[+(\s+)(\S*\$\S*PV\S*)(\s+)(\S+)(\s+)(\S+)(\s+)\]+([^]])|\1\[\[\2\3\4\5\6\7\8\]\]\9|g' \
{} \+
find -name '*.ebuild' -exec sed -i -E \
's|\[(\s+)(\S*\$\S*PV\S*)(\s+)==?(\s+)(\S+)(\s+)\]|\[\1\2\3==\4\5\6\]|g' \
{} \+
```
this is aimed to be a series of commits meant to replace all instance of
POSIX [ ... ] to bash's [[ ... ]], to make guru up to date with the
coding style guide
this process is divided up into a series of commits in order to make
review and testing more easy
Signed-off-by: ingenarel (NeoJesus) <ingenarel_neojesus@disroot.org>
Part-of: https://codeberg.org/gentoo/guru/pulls/6
Signed-off-by: Michał Górny <mgorny@gentoo.org>
Currently, the version in the tree is OLD. And when I was about to do an
update on my system, obviously it wanted to enable python 3.13 for this
package. Because it is a dependency of qman.
This version is compatible with python 3.14, tests ran fine, and qman
also compiles and runs fine with this version
Signed-off-by: ingenarel (NeoJesus) <ingenarel_neojesus@disroot.org>
Recently I had to fix bug 975031, which was the same issue. Hardcoded
target/release paths in the ebuilds for rust projects. And this will
fail if the debug use flag is enabled. Because then, instead of
target/release, rust compiles the binary to target/debug
using cargo_target_dir from the cargo.eclass fixes this problem
It does not touch some ebuilds tho because for some I wasn't fully sure
if I should change the paths, and for some I wanted to do it in a
separate commit
Signed-off-by: ingenarel (NeoJesus) <ingenarel_neojesus@disroot.org>
Part-of: https://codeberg.org/gentoo/guru/pulls/21
Signed-off-by: Michał Górny <mgorny@gentoo.org>
David Roman