You are not logged in.
Pages: 1
I am currently running dwm. I followed the abs intall method from the ArchWiki, but have run into trouble when I attempt to make changes to the config.h and recompile. If I make a single simple change to config.h (ex. change the value of "static const char ...color" or "static unsigned int borderpx") I do not notice any change in dwm upon restarting it.
[filam@lotte dwm]$ makepkg -efi
==> Making package: dwm 5.3-1 i686 (Tue Dec 30 11:47:02 EST 2008)
==> Checking Runtime Dependencies...
==> Checking Buildtime Dependencies...
==> WARNING: Skipping source retrieval -- using existing src/ tree
==> WARNING: Skipping source integrity checks -- using existing src/ tree
==> WARNING: Skipping source extraction -- using existing src/ tree
==> Removing existing pkg/ directory...
==> Entering fakeroot environment...
==> Starting build()...
dwm build options:
CFLAGS = -std=c99 -pedantic -Wall -Os -I. -I/usr/include -I/usr/include/X11 -DVERSION="5.3"
LDFLAGS = -s -L/usr/lib -lc -L/usr/lib/X11 -lX11
CC = cc
CC dwm.c
CC -o dwm
dwm build options:
CFLAGS = -std=c99 -pedantic -Wall -Os -I. -I/usr/include -I/usr/X11R6/include -DVERSION="5.3"
LDFLAGS = -s -L/usr/lib -lc -L/usr/X11R6/lib -lX11
CC = cc
installing executable file to /home/filam/dwm/pkg/usr/bin
installing manual page to /home/filam/dwm/pkg/usr/share/man/man1
==> Tidying install...
-> Compressing man pages...
-> Stripping debugging symbols from binaries and libraries...
==> Creating package...
-> Generating .PKGINFO file...
-> Adding install script...
-> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: dwm 5.3-1 i686 (Tue Dec 30 11:47:04 EST 2008)
==> Installing package dwm with pacman -U...
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
Password:
filam is not in the sudoers file. This incident will be reported.
As a reletively new end-user I can imagine I have made some simple mistake, but just can't imagine what that might be.
Last edited by filam (2008-12-30 16:57:29)
Offline
pacman needs root privis when it installs a package, run that command as root, or add your user account to /etc/sudoers
Offline
==> ERROR: Running makepkg as root is a BAD idea and can cause
permanent, catastrophic damage to your system. If you
wish to run as root, please use the --asroot option.
What should I add to /etc/sudoers?
I imagine I don't want to do this:
filam ALL=(ALL) ALL
The sudoers man page looks rather long. I'll check in the morning (in 6 hours).
Last edited by filam (2008-12-30 07:12:23)
Offline
filam ALL=(ALL) ALL is correct, but it does give you full root priviledges if you run sudo, so you're good to be cautious
I run sudo makepkg when installing ABS packages, after all it does need root priviledges to install stuff system wide, but I'll let others chime in if theres a better way
Offline
You need root privs to install packages but you don't need them in order to create packages. You are running `makepkg -efi` which will try to install the package after its creation. The solution is simple, first create the package as a regular user via `makepkg -ef` (the `i` flag has been stripped), then, log in as root and run `pacman -U /full/path/to/your/newly/created/package`.
Last edited by string (2008-12-30 07:21:23)
Offline
I've seen a lot of people who use dwm installed to their home directory, outside of pacman, as it is only one binary that can be placed in ~/bin. This cuts down on the reinstallation, for instance.
Offline
Thanks for the help lake.
You need root privs to install packages but you don't need them in order to create packages. You are running `makepkg -efi` which will try to install the package after its creation. The solution is simple, first create the package as a regular user via `makepkg -ef` (the `i` flag has been stripped), then, log in as root and run `pacman -U /full/path/to/your/newly/created/package`.
Thanks string. Perfect explanation. This solution was exactly what I was looking for. Worked like a charm.
Offline
I imagine I don't want to do this:
filam ALL=(ALL) ALL
The sudoers man page looks rather long. I'll check in the morning (in 6 hours).
You're right. You don't want to add that. Ever.
Last edited by moljac024 (2008-12-30 17:28:24)
The day Microsoft makes a product that doesn't suck, is the day they make a vacuum cleaner.
--------------------------------------------------------------------------------------------------------------
But if they tell you that I've lost my mind, maybe it's not gone just a little hard to find...
Offline
I've seen a lot of people who use dwm installed to their home directory, outside of pacman, as it is only one binary that can be placed in ~/bin. This cuts down on the reinstallation, for instance.
I would advise doing this. I have dwm set up this way and it works nicely in terms of config.h control, installation, and upgrading.
br0tat0chip in #archlinux and on freenode
Offline
I too run dwm from ~/bin, certainly this is the way to go since the binary is personal - it contains your configuration.
BUT, when I do makepkg -i the package gets built as my normal user, and then the installation magically happens through sudo. I don't think I have anything special configured for this, other than having fakeroot installed.
All of your mips are belong to us!!
Offline
Pages: 1