You are not logged in.
Well, this is the first time i install a package from AUR, so I'm sorry for this newbie question, but I downloaded the dwm package from AUR and I can't find any dwm.c or config.def.h.
how i get the package :
curl -L https://aur.archlinux.org/cgit/aur.git/snapshot/dwm.tar.gz | tar zxI entered the dwm directory and I only have these files : config.h dwm dwm.install PKGBUILD
Dwm website is telling me to copy the config.def.h into config.h but I don't have any, and I found an interesting customization for the dwm.c but I can't find this, too. So, what could I miss ?
Last edited by Cookie23 (2018-10-24 15:29:49)
Offline
Welcome to the BBS.
This is covered well elsewhere on these boards, but very thoroughly on the AUR wiki page.
Research is a virtue!
All the best,
-HG
Offline
Thanks for the response, ... yes I read too quickly, I thought makepkg would directly make a binary^^ sorry for that.
Offline
C'est la vie. Do read more carefully next time; Arch expects you to mostly fend for yourself (albeit with the aid of reasonable documentation and a mostly consistent system).
Please also remember to mark your thread as solved.
All the best,
-HG
Offline
I thought makepkg would directly make a binary
It will. But that's not all it does.
For most packages, you'd just run makepkg (likely with flags like -s or -si) in the directory with the PKGBUILD. But with many suckless packages (e.g., dwm, st) you will likely want to modify the source files before building (e.g., config.def.h). So in these cases you'd use makepkg to obtain the source (makepkg -so) then modify anything in the src folder as needed, then complete the build (makepkg -e).
Many of us who use suckless tools will keep our own PKGBUILD around that automates the above with our own patches so updating is easier. (Personally I use a short sed script for st, so I just add a line like `sed -if /path/to/my/st.sed config.h` to the prepare function of the PKGBUILD).
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
For most packages, you'd just run makepkg (likely with flags like -s or -si) in the directory with the PKGBUILD. But with many suckless packages (e.g., dwm, st) you will likely want to modify the source files before building (e.g., config.def.h). So in these cases you'd use makepkg to obtain the source (makepkg -so) then modify anything in the src folder as needed, then complete the build (makepkg -e).
Many of us who use suckless tools will keep our own PKGBUILD around that automates the above with our own patches so updating is easier. (Personally I use a short sed script for st, so I just add a line like `sed -if /path/to/my/st.sed config.h` to the prepare function of the PKGBUILD).
Thanks for making it clear
Offline