Fixes these pkgcheck warnings:
BadDescription: version 1.8.1: DESCRIPTION="A very fast implementation
of tldr in Rust." ends with a full stop
BadDescription: version 1.9.0: DESCRIPTION="A very fast implementation
of tldr in Rust." ends with a full stop
BadDescription: version 9999: DESCRIPTION="A very fast implementation
of tldr in Rust." ends with a full stop
Signed-off-by: ingenarel (NeoJesus) <ingenarel_neojesus@disroot.org>
as per the coding style guide:
https://projects.gentoo.org/qa/policy-guide/ebuild-format.html#pg0101
The changes were generated using these two commands:
```
find -name '*.ebuild' -exec sed -i -E \
's|(\s+)\[+(\s+)(\S+)(\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+)==?(\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
Merges: 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
change all instances of [ "$(use doc)" ] to [[ "$(use doc)" ]]
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
change all instance of
[ "$(go env GOARM)" != '' ] to
[[ "$(go env GOARM)" != '' ]]
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
change all instance of
[ "$e" != "./exe/stringifor_test_parse_large_csv" ] to
[[ "$e" != "./exe/stringifor_test_parse_large_csv" ]]
The changes were generated using these two commands:
```
find -name '*.ebuild' -exec sed -i -E \
's|(\s+)\[+(\s+)(\S+)(\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+)==?(\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>
as per the coding style guide:
https://projects.gentoo.org/qa/policy-guide/ebuild-format.html#pg0101
The changes were generated using these two commands:
```
find -name '*.ebuild' -exec sed -i -E \
's|(\s+)\[+(\s+)(\S+)(\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+)==?(\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>
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>
Fixes these pkgcheck warnings:
```
❯ pkgcheck scan --net
gui-apps/satty
BadDescription: version 0.20.1: DESCRIPTION="A screenshot annotation tool inspired by Swappy and Flameshot." ends with a full stop
BadDescription: version 9999: DESCRIPTION="A screenshot annotation tool inspired by Swappy and Flameshot." ends with a full stop
```
Signed-off-by: ingenarel (NeoJesus) <ingenarel_neojesus@disroot.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>
The previous commits fixed instances where ebuilds weren't using
cargo_target_dir to get the target directory. But, was either using
hardcoded target/release paths, which would break if 'DEBUG' USE flag is
enabled, or it was using something else like
`usex debug debug release`
This commit quotes all the instances where cargo_target_dir is called in
a subshell. Because I was doing that anyway for the files I touched in
https://codeberg.org/gentoo/guru/pulls/21
Signed-off-by: ingenarel (NeoJesus) <ingenarel_neojesus@disroot.org>
Part-of: https://codeberg.org/gentoo/guru/pulls/21
Merges: https://codeberg.org/gentoo/guru/pulls/21
Signed-off-by: Michał Górny <mgorny@gentoo.org>
See the previous 2nd commit to see more info
for the files changed in this commit, there wasn't any problem with how
the path was being handled per se
however, it was getting the path via
```
target/$(usex debug debug release)
```
but cargo_target_dir from cargo.eclass already exists. Hence, I changed
it to this so the ebuilds in the tree are more consistent
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>
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>
!<app-editors/vim-core-9.1.1652-r1 was already nuked from ::gentoo on
https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d376ccdab25117f0edfde657eed0abd23ad6eb59
So currently, there's not really a need to explicitly declare that in here
Also fixes the current pkgcheck warnings:
dev-util/tinyxxd
NonexistentBlocker: version 1.3.16: nonexistent blocker RDEPEND="!<app-editors/vim-core-9.1.1652-r1": no matches in repo history
NonexistentBlocker: version 9999: nonexistent blocker RDEPEND="!<app-editors/vim-core-9.1.1652-r1": no matches in repo history
Signed-off-by: ingenarel (NeoJesus) <ingenarel_neojesus@disroot.org>
Recently did a EAPI change, and the ebuild command ran fine, so I
thought everything was fine
Now I've realized I should've run every ebuild phase instead of just the
pretend and unpack phases
Previously the ebuilds would fail because makeopts_jobs is banned in
EAPI 9, now it should work
Signed-off-by: ingenarel (NeoJesus) <ingenarel_neojesus@disroot.org>
I originally copied the compile command from the Makefile, and modified
it according to the needs
However, it originally was passing on the `-s` and `-w` flag to the go
linker
From https://pkg.go.dev/cmd/link
```
-s
Omit the symbol table and debug information.
Implies the -w flag, which can be negated with -w=0.
-w
Omit the DWARF symbol table.
```
So when the install phase happened, portage was complaining about pre
stripped files
This should be fixed now
Thanks goes to ago for finding this bug!
Closes: https://bugs.gentoo.org/977875
Signed-off-by: ingenarel (NeoJesus) <ingenarel_neojesus@disroot.org>
Changes done to: 9999, 0.11.0 -> 0.11.0-r1
all changes that are listed here apply to both of the versions
- Previously I was assigning
$(llvm_gen_dep 'llvm-core/clang:${LLVM_SLOT}')
in DEPEND, that was a mistake on my part. it should've been in
BDEPEND. because clang is actually being executed in the compile phase
to get the "libclang_rt.fuzzer-${CHOST%%-*}.a" path
On top of that, another mistake was thinking that libclang_rt.fuzzer
was actually being provided by the clang package. instead it was being
provided by the llvm-runtimes/compiler-rt-sanitizers[libfuzzer]
package
so that's inside DEPEND now.
Huge thanks to gonsoos for pointing this out to me in
https://github.com/gentoo/guru/commit/651247c1b6a0319ec9ab0aeb95e6e3da2a2a62ca#r189289633
- A desktop file was also being provided that I didn't notice.
The ebuilds install that now
Huge thanks to TimovVeen for pointing this out to me in
https://github.com/gentoo/guru/commit/651247c1b6a0319ec9ab0aeb95e6e3da2a2a62ca#r189405830
- instead of having references to files like
`target/completions/rmpc.bash`
it now uses
`target/completions/"${PN}".bash`
Signed-off-by: ingenarel (NeoJesus) <ingenarel_neojesus@disroot.org>
I don't usually do cleanups for old versions for packages that I don't
maintain
however I have tried to contact ephemer4l myself via their email, and
it's been a while. And they haven't responded, the last 7 commits was
also from me, and the previous PRs that I did about this package was
also unnoticed by them, and I later just merged it with pram myself
Signed-off-by: ingenarel (NeoJesus) <ingenarel_neojesus@disroot.org>
Another thanks to Agostino Sarubbo for finding this bug
code is mostly copy pasted from the nim_gen_config() function from
nim-utils.eclass, modified a bit to actually append to the original
nim.cfg, instead of replacing it
This should hopefully, fix the issue. With my testing, I tested by
setting the compiler to clang and then GCC, and thankfully when I
checked btop, nimc was actually using the appropriate compiler
Closes: https://bugs.gentoo.org/975973
Signed-off-by: ingenarel (NeoJesus) <ingenarel_neojesus@disroot.org>
As per the devmanual, ${DEPEND} has been moved from ${BDEPEND}, because
> BDEPEND specifies dependencies applicable to CBUILD, i.e. programs that
> need to be executed during the build, e.g. virtual/pkgconfig. DEPEND
> specifies dependencies for CHOST, i.e. packages that need to be found on
> built system, e.g. libraries and headers.
On top of that, a proper ${RDEPEND} has also been set, as it didn't
contain the necessary dependencies, which was found by Agostino Sarubbo
Closes: https://bugs.gentoo.org/975673
Signed-off-by: ingenarel (NeoJesus) <ingenarel_neojesus@disroot.org>
Thanks, Agostino Sarubbo for finding the test phase and install phase
bugs
- sys crate fixes were generated using:
https://codeberg.org/ingenarel-NeoJesus/apply-crates-fixes/commit/50826abbf4cc94405069956bd817b9b6ab627fb0
and it's deps fixes are for the same reason as commit
6c4a37fb4c
- more test skips are added, either because they need the internet, or
it's an actual upstream problem that would be hard for me to patch in
downstream. `--no-fail-test` flag is also added to run all tests even
if any fails, in order to get the full list of failed tests, which
makes it easier to bump and maintain
- changed the hardcoded target/release paths to $(cargo_target_dir),
that way it doesn't fail if DEBUG USE is set.
Closes: https://bugs.gentoo.org/975031
Closes: https://bugs.gentoo.org/975032
Signed-off-by: ingenarel (NeoJesus) <ingenarel_neojesus@disroot.org>
Thanks Agostino Sarubbo for finding this bug
fixes were generated using:
https://codeberg.org/ingenarel-NeoJesus/apply-crates-fixes/commit/50826abbf4cc94405069956bd817b9b6ab627fb0
To keep things easier for me and the tool, I didn't put zstd in
something like ${COMMON_DEPS} and put then in both ${RDEPEND} and in
${DEPEND}.
As I would either need to manually update it after every fix by the
fixing script, or update the scripting fix to support the logic to
realize what deps are common, which imho is a bit overkill for a bash
script that's already complicated
Closes: https://bugs.gentoo.org/975161
Signed-off-by: ingenarel (NeoJesus) <ingenarel_neojesus@disroot.org>
currently tests are disabled because superfile tends to create files in
places it should not:
https://gist.githubusercontent.com/ingenarel/d1bc358ee532d5d3a50f5cc19c429253/raw
on top of that it has failed tests, tests depend on zoxide, tmux,
python, a few python modules
and everything would also require some patching
the goal is to work on a src_test function slowly and bring back tests
again, but for now, tests should be restricted because it may cause
issues
Closes: https://bugs.gentoo.org/974530
Signed-off-by: ingenarel (NeoJesus) <ingenarel_neojesus@disroot.org>
updates:
- licenses: properly separate and update the go module licenses so it's
easier to see which is for which
fixes:
- src_test: previously running test didn't do anything. It should be
fixed now, and ego test should run the proper tests
adds:
- man page installation
- shell completions installation for bash, zsh, and fish
Signed-off-by: ingenarel (NeoJesus) <ingenarel_neojesus@disroot.org>
cargo_src_install was triggering recompiling in the src_install phase,
this should not do that now
Signed-off-by: ingenarel (NeoJesus) <ingenarel_neojesus@disroot.org>
previous versions was patching the source code to manually rip out the
code related to online tests
these versions use CARGO_SKIP_TESTS instead, making the process much
easier to maintain, test, bump, and, if need arises, easier to
re-enable/disable patches again
Signed-off-by: ingenarel (NeoJesus) <ingenarel_neojesus@disroot.org>
randomly found this gem of a file conflict out when I was recently
installing nodejs with the corepack use flag to test out a few software
and add the packages
lo and behold, nodejs failed to install on the src_install phase because
of file collision, and i saw that pnpm-bin was the issue because it
wasn't blocking nodejs[corepack]
one could easily check this by doing
```
❯ equery f nodejs | grep -e '/usr/bin/'
/usr/bin/corepack
/usr/bin/node
/usr/bin/npm
/usr/bin/npx
/usr/bin/pnpm
/usr/bin/pnpx
/usr/bin/yarn
/usr/bin/yarnpkg
```
this commit should fix this issue
Signed-off-by: ingenarel (NeoJesus) <ingenarel_neojesus@disroot.org>
Part-of: https://codeberg.org/gentoo/guru/pulls/12
