To view parent comment, click here.
To read all comments associated with this story, please click here.
"For one thing it doesn't need to be compiled from source by the user, nor do the packages."
Slackware doesn't either, but you don't need to go hunting -dev packages there. And source based distributions by their very nature include everything needed as well. This avoids episodes like this: http://lists.ximian.com/pipermail/gtk-sharp-list/2006-August/007317...
While neither all of the 21 articles in the wiki, or the 12 topics on the forums have anything to say on the subject, judging by http://ftp.arklinux.org you don't have it any more convenient.
"Secondly it's still easy to use as long as users have supported hardware and aren't so lazy they wouldn't breathe if they had a choice. It even has graphical configuration tools that the user can choose to, or not to use without breaking one method in order for the other to work."
Which can be said of most distros out there, except maybe LFS. It IS 2006, you know.
"But most importantly, it uses RPM, and adheres to standards to make developing the distribution, and distributing software to users easier."
I assume you're referring to the LSB? The only other 'standards' are de facto at best. I'm unconvinced about the superiority of the RPM format.
Edited 2006-08-04 19:37
"Which can be said of most distros out there, except maybe LFS. It IS 2006, you know. "
Actually a lot of distributions have graphical configuration tools which break manual configuration, SUSE's yast for example. Even Lycoris would drop custom settings on me when the configuration tools were run. What I was pointing out about Ark Linux is that the graphical configuration tools won't exclude the possibility of also doing manual configuration, whereas in some distributions the two are often mutually exclusive.
"I assume you're referring to the LSB? The only other 'standards' are de facto at best. I'm unconvinced about the superiority of the RPM format. "
No, I'm referring to standards such as where devices are mounted. In the Ubuntu family as well as a handfull of other distributions the location is in /media, while the norm in Linux used to always be /mnt. Mandriva has it's own way of handling the KDE menu which is frustrating to people who can't find any working documentation on how to use it and can't get any help working with it. Those are the kinds of standards I'm talking about.
Adhering to standards on paper is usually not a problem, it's the unregulated subtleties that different distributions do that frustrate and annoy people.




Member since:
2005-06-29
"So how is it actually better than Slackware for devs? Or Gentoo?"
For one thing it doesn't need to be compiled from source by the user, nor do the packages. Secondly it's still easy to use as long as users have supported hardware and aren't so lazy they wouldn't breathe if they had a choice. It even has graphical configuration tools that the user can choose to, or not to use without breaking one method in order for the other to work. But most importantly, it uses RPM, and adheres to standards to make developing the distribution, and distributing software to users easier.