Re:Arch Linux – "It is what you make it"
by pavpanchekha on Friday September 16, 2011 @10:29PM
(#3007049)
It may also be that figuring out the entire Ubuntu stack is near-impossible, whereas with Arch this is at least approachable.
No package manager should use /usr/local/.
Re:Arch Linux – "It is what you make it"
by fakeempire on Saturday September 17, 2011 @01:06AM
(#3007298)
would you elaborate? i guess i agree for historical reasons but for practical reasons i think package managers actually should use /usr/local/. basically everyone uses a package manager now (except lfs). where would you like package managers to install.
Re:Arch Linux – "It is what you make it"
by lvillani on Saturday September 17, 2011 @06:40AM
(#3007739)
From the FHS:
"The /usr/local hierarchy is for use by the system administrator when installing software locally. It needs to be safe from being overwritten when the system software is updated." [1]
And I believe that "system software" today means "installed by a package manager" (please correct me if I'm wrong).
I personally (rarely) use /usr/local for manually-installed packages. This way there's no risk of a package manager accidentally overwriting stuff outside its control.
[1] http://www.pathname.com/fhs/pub/fhs-2.3.html#THEUSRHIERARCHY
"It really does take time" most likely refers to the fact that you are responsible for building up the OS yourself. So unlike in an OS like Ubuntu, where you do not have to know what a window manager is, or what an xorg xserver and client means, you'll have to learn it all along the way.
Fortunately the wiki makes figuring everything out managable, and I found it an enjoyable to spend a couple days with different software[1] and a programmable tiling window manager[2]. The end result is a fast-booting custom tailored system.
[1] https://wiki.archlinux.org/index.php/Lightweight_Application... [2] http://awesome.naquadah.org/