On Sun, 2022-02-27 at 03:40 +0100, Adam Borowski wrote:
> Among others, "command -v"
[...]
> * built-ins get reported as available. And busybox has even "dpkg"
> built-in, with a pretty bad implementation.
Like this?
+---
| % which which
| which: shell built-in command
+---
I suggest to imple
On 2022-02-27 Adam Borowski wrote:
> On Sun, Feb 27, 2022 at 01:40:48AM +0100, Ben Hutchings wrote:
[...]
>> This should use "command -v", not which, I think?
> No, and the recent debacle revealed enough reasons that I'm pondering a MBF
> to change that _back_ in packages which followed the bad a
On Sun, Feb 27, 2022 at 03:40:09AM +0100, Adam Borowski wrote:
> No, and the recent debacle revealed enough reasons that I'm pondering a MBF
> to change that _back_ in packages which followed the bad advice.
do you have a # as a starter?
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debi
On Sun, Feb 27, 2022 at 01:40:48AM +0100, Ben Hutchings wrote:
> On Sun, 2022-02-20 at 22:43 +0100, Adam Borowski wrote:
> > if which valgrind >/dev/null; then
>
> This should use "command -v", not which, I think?
No, and the recent debacle revealed enough reasons that I'm pondering a MBF
to chan
On Sun, 2022-02-20 at 22:43 +0100, Adam Borowski wrote:
> On Sun, Feb 20, 2022 at 04:32:43PM -0500, Jeremy Bicha wrote:
> > On Sun, Feb 20, 2022 at 1:46 PM Adam Borowski wrote:
> > > The correct answer currently is:
> > > [amd64 arm64 armhf i386 mips64el mipsel ppc64el s390x powerpc ppc64]
> >
On Sun, 2022-02-20 at 19:45 +0100, Adam Borowski wrote:
> A lot of packages Build-Depend on valgrind, in order to run checks for
> memory leaks, data races and what not during the testsuite. Alas, valgrind
> is not available on some architectures, even release (armel) or want-to-be-
> release (ri
On Sun, Feb 20, 2022 at 1:46 PM Adam Borowski wrote:
> The correct answer currently is:
> [amd64 arm64 armhf i386 mips64el mipsel ppc64el s390x powerpc ppc64]
> but it keeps changing, and you don't want to track it by hand if I can do
> that for you.
>
> Thus: please [b-]depend on valgrind-if-
On Sun, Feb 20, 2022 at 04:32:43PM -0500, Jeremy Bicha wrote:
> On Sun, Feb 20, 2022 at 1:46 PM Adam Borowski wrote:
> > The correct answer currently is:
> > [amd64 arm64 armhf i386 mips64el mipsel ppc64el s390x powerpc ppc64]
> > but it keeps changing, and you don't want to track it by hand i
Hi ladies and gentelhackers!
A lot of packages Build-Depend on valgrind, in order to run checks for
memory leaks, data races and what not during the testsuite. Alas, valgrind
is not available on some architectures, even release (armel) or want-to-be-
release (riscv64). Keeping the list current r
9 matches
Mail list logo
