Arch Linux

Atterratio

Member

Registered: 2011-08-22

Posts: 6

Registration config files in "home" directories.

People, how you think, it's a good idea, to add in PKGBUILD information about created, by the program, settings in your home directory? And also add a key, allowing Pacman to remove them?

Last edited by Atterratio (2011-11-13 04:56:14)

.:B:.

Forum Fellow

Registered: 2006-11-26

Posts: 5,819

Website

Re: Registration config files in "home" directories.

Arch rule of thumb: don't mess with the user's system for configuration. Install the package, leave configuration up to the user. If you want to provide user configuration files you can always use /etc/skel/.

---

Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy

Atterratio

Member

Registered: 2011-08-22

Posts: 6

Re: Registration config files in "home" directories.

I think you don't understand my message. I don't want to write configuration files, the more the system's. I propose register configuration files of various applications and provide easy cleanup when removed and easy way reset their settings.

Ofcourse I forgot say sorry fo my English *(T_T)*

Leonid.I

Member

From: Aethyr

Registered: 2009-03-22

Posts: 999

Re: Registration config files in "home" directories.

I think you don't understand my message. I don't want to write configuration files, the more the system's. I propose register configuration files of various applications and provide easy cleanup when removed and easy way reset their settings.

Ofcourse I forgot say sorry fo my English *(T_T)*

No, he did understand. pacman or any other pkg  manager deals with system-wide configs, not per-user ones. If you need to set some "lowest default" configs for your users use /etc/skel (google it if you don't know what that is).

---

Arch Linux is more than just GNU/Linux -- it's an adventure
pkill -9 systemd

n0stradamus

Member

Registered: 2010-11-08

Posts: 94

Website

Re: Registration config files in "home" directories.

Arch rule of thumb: don't mess with the user's system for configuration. Install the package, leave configuration up to the user. If you want to provide user configuration files you can always use /etc/skel/.

I agree. I always keep my configuration files if an application has proven useful and I don't need it anymore for the moment. Perhaps I might come back to it again and then I'd be able to reuse my config.