You are not logged in.
Pages: 1
I just want to know if this is like slackware as in it doesn't change packages and stuff. I hope this isn't another debain clone....
Offline
Offline
it is not like Slack, since it (Arch) handles dependencies and conflicting packages. However, it is not a Debian clone.
Offline
The packages in Arch are much more up to date and bleeding edge than Slack. It is similar to slack in that it is based on the simple and well architected BSD-like init scripts. I am also a Slack user that recently stumbled upon Arch and I absolutelly love it.
Offline
There's no heavy patching of packages -- which is what I think the OP was alluding to when comparing Arch to Debian.
Offline
arch is stable as slack , have a good package system as debian , and give you a chance to choose what are you want.. binary or source pkgs as gentoo What else we can want?!
Offline
Correction Arch "can" be as stable as slack and has a "better" package manager than debian. Well thats just my view anyway.
Offline
Agree 8)
Offline
There's no heavy patching of packages -- which is what I think the OP was alluding to when comparing Arch to Debian.
thanks thats all I needed to know
Offline
allucid wrote:There's no heavy patching of packages -- which is what I think the OP was alluding to when comparing Arch to Debian.
thanks thats all I needed to know
Let's put it this way. When there's patching done to a source here, you can see for yourself what the patching is and recompile without the patches you don't like if you want. Take a look at Arch's ABS stuff. When you look inside a PKGBUILD for a particular package, you'll explicitly see all the patches, if any, that are applied to the source before compiling. If you don't like them, you can recompile the entire package with its PKBUILD after editing that file to remove the patches. Recompiling when you have a PKBUILD is as simple as running makepkg. Then you just use pacman to install the newly created package.
Offline
allucid wrote:There's no heavy patching of packages -- which is what I think the OP was alluding to when comparing Arch to Debian.
thanks thats all I needed to know
It would be wrong to say that there is no patching. There are many patches these days to make packages compile with gcc 4.1. And sometimes a feature is broken, so it has to be fixed. Our kernel sometimes has backports from newer versions when someone complains that a driver or feature is broken.
But that is not heavy patching. Just take a look at some PKGBUILDs: http://cvs.archlinux.org/cgi-bin/viewcvs.cgi/
Offline
Oh jeez ... and it's true. Even debian sarge takes soooo long to load compared to Arch. Makes you wonder what all the complexity is for - they both do the same thing regardless of weight ...
Offline
? I haven't had sarge take 'soooo' long to do anything.
I have sooooo grown to hate these kind of topics.
"Be conservative in what you send; be liberal in what you accept." -- Postel's Law
"tacos" -- Cactus' Law
"t̥͍͎̪̪͗a̴̻̩͈͚ͨc̠o̩̙͈ͫͅs͙͎̙͊ ͔͇̫̜t͎̳̀a̜̞̗ͩc̗͍͚o̲̯̿s̖̣̤̙͌ ̖̜̈ț̰̫͓ạ̪͖̳c̲͎͕̰̯̃̈o͉ͅs̪ͪ ̜̻̖̜͕" -- -̖͚̫̙̓-̺̠͇ͤ̃ ̜̪̜ͯZ͔̗̭̞ͪA̝͈̙͖̩L͉̠̺͓G̙̞̦͖O̳̗͍
Offline
Pages: 1