During the majority of my time working with computers, Windows was the operating system of choice. Reason being, it's all I've known. In 2002, I took a college course titled "Linux Administration" which entitled me to a few cd-roms of Redhat 7.x. While this course was nothing more than a few extra credits for me, I fell in love with Linux and went through the entire textbook a week into the class. It was a nice feeling to use something "different" than what I was used to.
Permalink for comment
To read all comments associated with this story, please click here.
Sounds like you need FreeBSD...
FreeBSD has a huge online repository of precompiled applications & has no problem resolving dependencies. It's as simple as selecting them from the list and pressing install.
Why do people keep touting alternatives when RPM distributions deal with dependencies just fine, as long as you stick with RPMs for one distribution.
If the commercial distributions had adopted .deb, different .deb trees would be just as incompatible as different RPM trees.
And yes, the same problems would probably arise if there were a RedHat FreeBSD, a SuSE FreeBSD, a Mandrake FreeBSD, ... .
The problem isn't with the package format or the package tools, it's with the missing standard for the actual packages.
Sounds like you need FreeBSD...
FreeBSD has a huge online repository of precompiled applications & has no problem resolving dependencies. It's as simple as selecting them from the list and pressing install.
Why do people keep touting alternatives when RPM distributions deal with dependencies just fine, as long as you stick with RPMs for one distribution.
If the commercial distributions had adopted .deb, different .deb trees would be just as incompatible as different RPM trees.
And yes, the same problems would probably arise if there were a RedHat FreeBSD, a SuSE FreeBSD, a Mandrake FreeBSD, ... .
The problem isn't with the package format or the package tools, it's with the missing standard for the actual packages.