Post History
This answer is not directly usable under Arch, since I don't know the tools there. I show you a way to do it on Debian, which may inspire you to find a similar way in Arch. With apt-file(1), you ...
Answer
#8: Post edited
- This answer is not directly usable under Arch, since I don't know the tools there. I show you a way to do it on Debian, which may inspire you to find a similar way in Arch.
With *apt-file*(1), you can list the files that a package provides. From that list, you can see if the package provides files in `/usr/bin/` or in `/usr/lib/`. It's not a perfect approach, since it may provide files in both, in which case you're on your own. Of course, in Debian it would be easier, as libraries are named using `lib*` for runtimes, and `lib*-dev` for development files, but this is just for demonstration of the technique. Also, it's not always clear, as some packages provide both libraries and binaries.- ```sh
- $ apt-file show libncurses-dev \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- libncurses-dev: /usr/bin/ncurses6-config
- libncurses-dev: /usr/lib/valgrind/ncurses.supp
- $ apt-file show libncurses6 \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- libncurses6: /usr/lib/x86_64-linux-gnu/libform.so.6
- $ apt-file show libbsd-dev \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- libbsd-dev: /usr/lib/x86_64-linux-gnu/libbsd-ctor.a
- $ apt-file show libbsd0 \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- libbsd0: /usr/lib/x86_64-linux-gnu/libbsd.so.0
- $ apt-file show coreutils \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- coreutils: /usr/bin/[
- $ apt-file show pass \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- pass: /usr/bin/pass
- ```
- This answer is not directly usable under Arch, since I don't know the tools there. I show you a way to do it on Debian, which may inspire you to find a similar way in Arch.
- With *apt-file*(1), you can list the files that a package provides. From that list, you can see if the package provides files in `/usr/bin/` or in `/usr/lib/`. It's not a perfect approach, since it may provide files in both, in which case you're on your own. Of course, in Debian it would be easier, as libraries are named using `lib*` for runtimes, and `lib*-dev` for development files, but this is just for demonstration of the technique.
- ```sh
- $ apt-file show libncurses-dev \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- libncurses-dev: /usr/bin/ncurses6-config
- libncurses-dev: /usr/lib/valgrind/ncurses.supp
- $ apt-file show libncurses6 \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- libncurses6: /usr/lib/x86_64-linux-gnu/libform.so.6
- $ apt-file show libbsd-dev \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- libbsd-dev: /usr/lib/x86_64-linux-gnu/libbsd-ctor.a
- $ apt-file show libbsd0 \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- libbsd0: /usr/lib/x86_64-linux-gnu/libbsd.so.0
- $ apt-file show coreutils \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- coreutils: /usr/bin/[
- $ apt-file show pass \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- pass: /usr/bin/pass
- ```
#7: Post edited
- This answer is not directly usable under Arch, since I don't know the tools there. I show you a way to do it on Debian, which may inspire you to find a similar way in Arch.
With *apt-file*(1), you can list the files that a package provides. From that list, you can see if the package provides files in `/usr/bin/` or in `/usr/lib/`. It's not a perfect approach, since it may provide files in both, in which case you're on your own. Of course, in Debian it would be easier, as libraries are named using `lib*` for runtimes, and `lib*-dev` for development files, but this is just for demonstration of the technique. Also, it's not always clear, as some packages provide bith libraries and binaries.- ```sh
- $ apt-file show libncurses-dev \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- libncurses-dev: /usr/bin/ncurses6-config
- libncurses-dev: /usr/lib/valgrind/ncurses.supp
- $ apt-file show libncurses6 \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- libncurses6: /usr/lib/x86_64-linux-gnu/libform.so.6
- $ apt-file show libbsd-dev \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- libbsd-dev: /usr/lib/x86_64-linux-gnu/libbsd-ctor.a
- $ apt-file show libbsd0 \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- libbsd0: /usr/lib/x86_64-linux-gnu/libbsd.so.0
- $ apt-file show coreutils \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- coreutils: /usr/bin/[
- $ apt-file show pass \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- pass: /usr/bin/pass
- ```
- This answer is not directly usable under Arch, since I don't know the tools there. I show you a way to do it on Debian, which may inspire you to find a similar way in Arch.
- With *apt-file*(1), you can list the files that a package provides. From that list, you can see if the package provides files in `/usr/bin/` or in `/usr/lib/`. It's not a perfect approach, since it may provide files in both, in which case you're on your own. Of course, in Debian it would be easier, as libraries are named using `lib*` for runtimes, and `lib*-dev` for development files, but this is just for demonstration of the technique. Also, it's not always clear, as some packages provide both libraries and binaries.
- ```sh
- $ apt-file show libncurses-dev \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- libncurses-dev: /usr/bin/ncurses6-config
- libncurses-dev: /usr/lib/valgrind/ncurses.supp
- $ apt-file show libncurses6 \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- libncurses6: /usr/lib/x86_64-linux-gnu/libform.so.6
- $ apt-file show libbsd-dev \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- libbsd-dev: /usr/lib/x86_64-linux-gnu/libbsd-ctor.a
- $ apt-file show libbsd0 \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- libbsd0: /usr/lib/x86_64-linux-gnu/libbsd.so.0
- $ apt-file show coreutils \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- coreutils: /usr/bin/[
- $ apt-file show pass \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- pass: /usr/bin/pass
- ```
#6: Post edited
- This answer is not directly usable under Arch, since I don't know the tools there. I show you a way to do it on Debian, which may inspire you to find a similar way in Arch.
With *apt-file*(1), you can list the files that a package provides. From that list, you can see if the package provides files in `/usr/bin/` or in `/usr/lib/`. It's not a perfect approach, since it may provide files in both, in which case you're on your own. Of course, in Debian it would be easier, as libraries are names using `lib*` for runtimes, and `lib*-dev` for development files, but this is just for demonstration of the technique. Also, it's not always clear, as some packages provide bith libraries and binaries.- ```sh
- $ apt-file show libncurses-dev \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- libncurses-dev: /usr/bin/ncurses6-config
- libncurses-dev: /usr/lib/valgrind/ncurses.supp
- $ apt-file show libncurses6 \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- libncurses6: /usr/lib/x86_64-linux-gnu/libform.so.6
- $ apt-file show libbsd-dev \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- libbsd-dev: /usr/lib/x86_64-linux-gnu/libbsd-ctor.a
- $ apt-file show libbsd0 \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- libbsd0: /usr/lib/x86_64-linux-gnu/libbsd.so.0
- $ apt-file show coreutils \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- coreutils: /usr/bin/[
- $ apt-file show pass \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- pass: /usr/bin/pass
- ```
- This answer is not directly usable under Arch, since I don't know the tools there. I show you a way to do it on Debian, which may inspire you to find a similar way in Arch.
- With *apt-file*(1), you can list the files that a package provides. From that list, you can see if the package provides files in `/usr/bin/` or in `/usr/lib/`. It's not a perfect approach, since it may provide files in both, in which case you're on your own. Of course, in Debian it would be easier, as libraries are named using `lib*` for runtimes, and `lib*-dev` for development files, but this is just for demonstration of the technique. Also, it's not always clear, as some packages provide bith libraries and binaries.
- ```sh
- $ apt-file show libncurses-dev \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- libncurses-dev: /usr/bin/ncurses6-config
- libncurses-dev: /usr/lib/valgrind/ncurses.supp
- $ apt-file show libncurses6 \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- libncurses6: /usr/lib/x86_64-linux-gnu/libform.so.6
- $ apt-file show libbsd-dev \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- libbsd-dev: /usr/lib/x86_64-linux-gnu/libbsd-ctor.a
- $ apt-file show libbsd0 \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- libbsd0: /usr/lib/x86_64-linux-gnu/libbsd.so.0
- $ apt-file show coreutils \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- coreutils: /usr/bin/[
- $ apt-file show pass \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- pass: /usr/bin/pass
- ```
#4: Post edited
- This answer is not directly usable under Arch, since I don't know the tools there. I show you a way to do it on Debian, which may inspire you to find a similar way in Arch.
- With *apt-file*(1), you can list the files that a package provides. From that list, you can see if the package provides files in `/usr/bin/` or in `/usr/lib/`. It's not a perfect approach, since it may provide files in both, in which case you're on your own. Of course, in Debian it would be easier, as libraries are names using `lib*` for runtimes, and `lib*-dev` for development files, but this is just for demonstration of the technique. Also, it's not always clear, as some packages provide bith libraries and binaries.
- ```sh
- $ apt-file show libncurses-dev \
| pee "grep -m1 '/usr/bin/'" "grep -m1 '/usr/lib/'"- libncurses-dev: /usr/bin/ncurses6-config
- libncurses-dev: /usr/lib/valgrind/ncurses.supp
- $ apt-file show libncurses6 \
| pee \"grep -m1 '/usr/bin/'" \"grep -m1 '/usr/lib/'";- libncurses6: /usr/lib/x86_64-linux-gnu/libform.so.6
- $ apt-file show libbsd-dev \
| pee \"grep -m1 '/usr/bin/'" \"grep -m1 '/usr/lib/'";- libbsd-dev: /usr/lib/x86_64-linux-gnu/libbsd-ctor.a
- $ apt-file show libbsd0 \
| pee \"grep -m1 '/usr/bin/'" \"grep -m1 '/usr/lib/'";- libbsd0: /usr/lib/x86_64-linux-gnu/libbsd.so.0
- $ apt-file show coreutils \
| pee \"grep -m1 '/usr/bin/'" \"grep -m1 '/usr/lib/'";- coreutils: /usr/bin/[
- $ apt-file show pass \
| pee \"grep -m1 '/usr/bin/'" \"grep -m1 '/usr/lib/'";- pass: /usr/bin/pass
- ```
- This answer is not directly usable under Arch, since I don't know the tools there. I show you a way to do it on Debian, which may inspire you to find a similar way in Arch.
- With *apt-file*(1), you can list the files that a package provides. From that list, you can see if the package provides files in `/usr/bin/` or in `/usr/lib/`. It's not a perfect approach, since it may provide files in both, in which case you're on your own. Of course, in Debian it would be easier, as libraries are names using `lib*` for runtimes, and `lib*-dev` for development files, but this is just for demonstration of the technique. Also, it's not always clear, as some packages provide bith libraries and binaries.
- ```sh
- $ apt-file show libncurses-dev \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- libncurses-dev: /usr/bin/ncurses6-config
- libncurses-dev: /usr/lib/valgrind/ncurses.supp
- $ apt-file show libncurses6 \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- libncurses6: /usr/lib/x86_64-linux-gnu/libform.so.6
- $ apt-file show libbsd-dev \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- libbsd-dev: /usr/lib/x86_64-linux-gnu/libbsd-ctor.a
- $ apt-file show libbsd0 \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- libbsd0: /usr/lib/x86_64-linux-gnu/libbsd.so.0
- $ apt-file show coreutils \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- coreutils: /usr/bin/[
- $ apt-file show pass \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- pass: /usr/bin/pass
- ```
#3: Post edited
- This answer is not directly usable under Arch, since I don't know the tools there. I show you a way to do it on Debian, which may inspire you to find a similar way in Arch.
- With *apt-file*(1), you can list the files that a package provides. From that list, you can see if the package provides files in `/usr/bin/` or in `/usr/lib/`. It's not a perfect approach, since it may provide files in both, in which case you're on your own. Of course, in Debian it would be easier, as libraries are names using `lib*` for runtimes, and `lib*-dev` for development files, but this is just for demonstration of the technique. Also, it's not always clear, as some packages provide bith libraries and binaries.
- ```sh
- $ apt-file show libncurses-dev \
- | pee "grep -m1 '/usr/bin/'" "grep -m1 '/usr/lib/'"
- libncurses-dev: /usr/bin/ncurses6-config
- libncurses-dev: /usr/lib/valgrind/ncurses.supp
- $ apt-file show libncurses6 \
| pee "grep -m1 '/usr/bin/'" "grep -m1 '/usr/lib/'"- libncurses6: /usr/lib/x86_64-linux-gnu/libform.so.6
- $ apt-file show libbsd-dev \
| pee "grep -m1 '/usr/bin/'" "grep -m1 '/usr/lib/'"- libbsd-dev: /usr/lib/x86_64-linux-gnu/libbsd-ctor.a
- $ apt-file show libbsd0 \
| pee "grep -m1 '/usr/bin/'" "grep -m1 '/usr/lib/'"- libbsd0: /usr/lib/x86_64-linux-gnu/libbsd.so.0
- $ apt-file show coreutils \
| pee "grep -m1 '/usr/bin/'" "grep -m1 '/usr/lib/'"- coreutils: /usr/bin/[
- $ apt-file show pass \
| pee "grep -m1 '/usr/bin/'" "grep -m1 '/usr/lib/'"- pass: /usr/bin/pass
- ```
- This answer is not directly usable under Arch, since I don't know the tools there. I show you a way to do it on Debian, which may inspire you to find a similar way in Arch.
- With *apt-file*(1), you can list the files that a package provides. From that list, you can see if the package provides files in `/usr/bin/` or in `/usr/lib/`. It's not a perfect approach, since it may provide files in both, in which case you're on your own. Of course, in Debian it would be easier, as libraries are names using `lib*` for runtimes, and `lib*-dev` for development files, but this is just for demonstration of the technique. Also, it's not always clear, as some packages provide bith libraries and binaries.
- ```sh
- $ apt-file show libncurses-dev \
- | pee "grep -m1 '/usr/bin/'" "grep -m1 '/usr/lib/'"
- libncurses-dev: /usr/bin/ncurses6-config
- libncurses-dev: /usr/lib/valgrind/ncurses.supp
- $ apt-file show libncurses6 \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- libncurses6: /usr/lib/x86_64-linux-gnu/libform.so.6
- $ apt-file show libbsd-dev \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- libbsd-dev: /usr/lib/x86_64-linux-gnu/libbsd-ctor.a
- $ apt-file show libbsd0 \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- libbsd0: /usr/lib/x86_64-linux-gnu/libbsd.so.0
- $ apt-file show coreutils \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- coreutils: /usr/bin/[
- $ apt-file show pass \
- | pee \
- "grep -m1 '/usr/bin/'" \
- "grep -m1 '/usr/lib/'";
- pass: /usr/bin/pass
- ```
#2: Post edited
- This answer is not directly usable under Arch, since I don't know the tools there. I show you a way to do it on Debian, which may inspire you to find a similar way in Arch.
- With *apt-file*(1), you can list the files that a package provides. From that list, you can see if the package provides files in `/usr/bin/` or in `/usr/lib/`. It's not a perfect approach, since it may provide files in both, in which case you're on your own. Of course, in Debian it would be easier, as libraries are names using `lib*` for runtimes, and `lib*-dev` for development files, but this is just for demonstration of the technique. Also, it's not always clear, as some packages provide bith libraries and binaries.
- ```sh
$ apt-file show libncurses-dev | pee "grep -m1 '/usr/bin/'" "grep -m1 '/usr/lib/'"- libncurses-dev: /usr/bin/ncurses6-config
- libncurses-dev: /usr/lib/valgrind/ncurses.supp
$ apt-file show libncurses6 | pee "grep -m1 '/usr/bin/'" "grep -m1 '/usr/lib/'"- libncurses6: /usr/lib/x86_64-linux-gnu/libform.so.6
$ apt-file show libbsd-dev | pee "grep -m1 '/usr/bin/'" "grep -m1 '/usr/lib/'"- libbsd-dev: /usr/lib/x86_64-linux-gnu/libbsd-ctor.a
$ apt-file show libbsd0 | pee "grep -m1 '/usr/bin/'" "grep -m1 '/usr/lib/'"- libbsd0: /usr/lib/x86_64-linux-gnu/libbsd.so.0
$ apt-file show coreutils | pee "grep -m1 '/usr/bin/'" "grep -m1 '/usr/lib/'"- coreutils: /usr/bin/[
$ apt-file show pass | pee "grep -m1 '/usr/bin/'" "grep -m1 '/usr/lib/'"- pass: /usr/bin/pass
- ```
- This answer is not directly usable under Arch, since I don't know the tools there. I show you a way to do it on Debian, which may inspire you to find a similar way in Arch.
- With *apt-file*(1), you can list the files that a package provides. From that list, you can see if the package provides files in `/usr/bin/` or in `/usr/lib/`. It's not a perfect approach, since it may provide files in both, in which case you're on your own. Of course, in Debian it would be easier, as libraries are names using `lib*` for runtimes, and `lib*-dev` for development files, but this is just for demonstration of the technique. Also, it's not always clear, as some packages provide bith libraries and binaries.
- ```sh
- $ apt-file show libncurses-dev \
- | pee "grep -m1 '/usr/bin/'" "grep -m1 '/usr/lib/'"
- libncurses-dev: /usr/bin/ncurses6-config
- libncurses-dev: /usr/lib/valgrind/ncurses.supp
- $ apt-file show libncurses6 \
- | pee "grep -m1 '/usr/bin/'" "grep -m1 '/usr/lib/'"
- libncurses6: /usr/lib/x86_64-linux-gnu/libform.so.6
- $ apt-file show libbsd-dev \
- | pee "grep -m1 '/usr/bin/'" "grep -m1 '/usr/lib/'"
- libbsd-dev: /usr/lib/x86_64-linux-gnu/libbsd-ctor.a
- $ apt-file show libbsd0 \
- | pee "grep -m1 '/usr/bin/'" "grep -m1 '/usr/lib/'"
- libbsd0: /usr/lib/x86_64-linux-gnu/libbsd.so.0
- $ apt-file show coreutils \
- | pee "grep -m1 '/usr/bin/'" "grep -m1 '/usr/lib/'"
- coreutils: /usr/bin/[
- $ apt-file show pass \
- | pee "grep -m1 '/usr/bin/'" "grep -m1 '/usr/lib/'"
- pass: /usr/bin/pass
- ```
#1: Initial revision
This answer is not directly usable under Arch, since I don't know the tools there. I show you a way to do it on Debian, which may inspire you to find a similar way in Arch. With *apt-file*(1), you can list the files that a package provides. From that list, you can see if the package provides files in `/usr/bin/` or in `/usr/lib/`. It's not a perfect approach, since it may provide files in both, in which case you're on your own. Of course, in Debian it would be easier, as libraries are names using `lib*` for runtimes, and `lib*-dev` for development files, but this is just for demonstration of the technique. Also, it's not always clear, as some packages provide bith libraries and binaries. ```sh $ apt-file show libncurses-dev | pee "grep -m1 '/usr/bin/'" "grep -m1 '/usr/lib/'" libncurses-dev: /usr/bin/ncurses6-config libncurses-dev: /usr/lib/valgrind/ncurses.supp $ apt-file show libncurses6 | pee "grep -m1 '/usr/bin/'" "grep -m1 '/usr/lib/'" libncurses6: /usr/lib/x86_64-linux-gnu/libform.so.6 $ apt-file show libbsd-dev | pee "grep -m1 '/usr/bin/'" "grep -m1 '/usr/lib/'" libbsd-dev: /usr/lib/x86_64-linux-gnu/libbsd-ctor.a $ apt-file show libbsd0 | pee "grep -m1 '/usr/bin/'" "grep -m1 '/usr/lib/'" libbsd0: /usr/lib/x86_64-linux-gnu/libbsd.so.0 $ apt-file show coreutils | pee "grep -m1 '/usr/bin/'" "grep -m1 '/usr/lib/'" coreutils: /usr/bin/[ $ apt-file show pass | pee "grep -m1 '/usr/bin/'" "grep -m1 '/usr/lib/'" pass: /usr/bin/pass ```