Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×
Mandriva Businesses

Debian's apt-get vs Mandrake's urpmi? 238

Deven Phillips asks: "I have been using Linux-Mandrake for quite a while now, and I wanted to know what Slashdotters think of the two rival package management systems available for Mandrake: apt and urpmi. I have been playing with both (apt is available in the Contribs section), and I have to say that so far urpmi is winning. I have always heard that apt-get is the best, so I am surprised by my conclusions. Am I missing something? Is apt for RPM not as mature as the deb counterpart?" I, for one, would have liked to have heard the reasons as to why Deven feels that urpmi is superior, but maybe there are a few of you out there who feel the same way, that can communicate this as well as he can. For those of you who have tried both, what features do you like out of the two of them, and which tool serves your needs the best?
This discussion has been archived. No new comments can be posted.

Debian's apt-get vs Mandrake's urpmi?

Comments Filter:
  • by mduell ( 72367 ) on Thursday June 28, 2001 @02:06PM (#121549)
    I just used it the other day for the first time, and pkg_add (on OpenBSD, and I'm sure a few others) is absolutely wonderful. All you have to type in is the full name of the tgz file, which can be on a local disk or an ftp server. NOTHING could be better than that!

    Moderators: I _hope_ you see the satire.

    Mark Duell
  • by Clay Mitchell ( 43630 ) on Thursday June 28, 2001 @02:06PM (#121550) Homepage
    Real men just download the entire contents of slackware-current :)

  • Slashdot: Bringing armies together for useless holy wars since 199x.
  • by VAXGeek ( 3443 ) on Thursday June 28, 2001 @02:07PM (#121552) Homepage
    Actually, I would say that the two packages are functionally equivalent, since the "cross pollination of ideas" was more than evident in this case. So, both Debian and Mandrakesoft can be commended in their creation of two very nice software management system. Most people would say that apt-get is the equivalent to the "install-anywhere" program so prevalent in Windows. Development of easy installation programs such as these help improve Linux's acceptance in the IS world today.
    ------------
    a funny comment: 1 karma
    an insightful comment: 1 karma
    a good old-fashioned flame: priceless
  • by Anonymous Coward
    I also have been using both for quite a while now, and although both have their strengths and weaknesses, urpmi wins out overall.

    Urpmi is less succeptable to broken dependancies than apt-get is, due to better design. Urpmi is also easier to integrate into a base distro than rpm due to the way the package database is maintained.

    Both have their strengths and weaknesses but for me, urpmi is my package management system of choice.
  • by 11thangel ( 103409 ) on Thursday June 28, 2001 @02:09PM (#121554) Homepage
    Mandrake 8 (and possibly earlier releases) comes with a tool called MandrakeUpdate. It's a rather nice GUI tool similar to Ximian Update, for all you gnome users. I haven't tried it much due to my 80 gig hdd croaking, but from what i saw it was pretty nice.
  • Nothing? So, say 'apt-get install ssh' couldn't be easier than 'pkg_add ssh-2.xx-commercial.tgz'? Hmm.

    Massochism is fine in the bedroom, but please keep the door closed so I don't have to watch. Thanks.
  • 1) Let's hope Mandrake never ships a broken PAM package as debian (albeit unstable) did a few days ago. For that alone, I'd give the edge to Mandrake, even though in practice, I've always enjoyed apt.

    2) Lets not forget the ports collection on FreeBSD. Installing a port is as easy as:

    locate (portname)

    cd /user/ports/(area)/(portname)

    make install
    All dependancies addressed for you. The port tree can be kept up to date with cvs. It's a great system. The maintainers seem to keep it relatively up to date, but just far enough behind that there are very few security scares.

  • mkdir /usr/ports That was easy, wasn't it?
  • by jmv ( 93421 ) on Thursday June 28, 2001 @02:13PM (#121558) Homepage
    Is emacs better than vi?
    Is gnome better than KDE?
    Is AMD better than Intel?
    Is Mandrake better than RedHat?
    Is red better than blue?

    OK, enough for now... Let the flames begin.
  • Asa frequent user of mandrake, I have to say that MandrakeUPdate is a very usefull and powerful tool. Nice GUI, ability to select Stable or Cooker (Development) updates, and good dependancy checking and filling make it awesome. apt-get is ok, but it lacks a fancy GUI. My favorite ssytem thouhg, howver, si the FreeBSD ports collection. Simply "make" the package, and it downloads and compiles the program, and any depdancies you need! Thus, you always have the source handy. I like this alot better then binary distribution systems.
  • Debian has not shipped a broken pam. :|
  • by krmt ( 91422 ) <therefrmhere@yah o o . com> on Thursday June 28, 2001 @02:17PM (#121561) Homepage
    When people talk about how great apt is, they're really talking about how great Debian as a whole is. One thing that really impressed me in to moving from Mandrake to Debian a while back was that Debian felt whole. It was a system, where Mandrake felt like a bunch of packages thrown together.

    With apt, you not only get your package dependencies solved along with the latest software, you get the work that was put in to making Debian a coherent system that adheres to the Debian policy. You get a specific maintainer for each package who will (almost) always respond promptly to emails about bugs and such. You can get a ton of help on Debian's mailing lists. You yourself can even become a maintainer if you've got the gusto to do so. Granted, Mandrake covers a lot of these areas (and has a nicer install) but Debian feels like a system, where every other distro I tried just felt like a bunch of packages. Granted, I haven't tried Mandrake in a while, but somehow I just don't think what they're doing will match up to Debian's volunteer maintainer model, even now.

    "I may not have morals, but I have standards."
  • There is a "fancy gui" in the form of a gtk/gnome frontend to apt-get.

    Also, apt-get has the option to download and compile source packages. I think it takes a couple more steps than the ports system, but it's not terribly complicated AFAIK (anyone wi/ more deb experience want to comment?)
  • by dbarclay10 ( 70443 ) on Thursday June 28, 2001 @02:17PM (#121563)
    When people say "apt-get" is best, they usually arn't referring to the tool itself. While it is a decent tool(as is dpkg, which is what does the actually package installation and maintenance), what really makes Debian so good is the packages themselves.

    All Debian packages are put together by volounteers. Of course, some get paid. But I don't know of any that are currently getting paid, that wern't volounteers first. apt-get is just a tool. What *really* makes the difference is the time spent on the packages themselves. Mandrake, Red Hat, and the rest only have so many people. Each has to take care of dozens of packages. They just can't spend as much time on them. In Debian, most of the ~7000 current packages, most maintainers just take care of two or three related packages. They usually use them, too. So most maintainers take their time and do things right.

    I'm not saying Red Hat or Mandrake arn't any good :) What I *am* saying is that the tool used to install the packages is a fairly minor issue. What's more important is the time the maintainers put into the packages themselves.

    That being said, apt-get was written from the ground up with dpkg in mind. It can be ported to use rpm(obviously), but I don't doubt that urpmi works better(when it comes to dealing with rpms) :)

    Barclay family motto:
    Aut agere aut mori.
    (Either action or death.)
  • I don't know much about dkpg, but everytimes I hear about it users seems very positive, I can't say so about urpmi.

    I'm using Mandrake 8.0, I've update quite a few packages from Mandrake's Cooker and now my systems doesn't work very well: I have to tell it twice otherwise it won't shutdown, I can't hear music anymore, etc...

    But who is the culprit urpmi or the packages?
    It's hard to tell!

    BTW I'm currently trying to uprade urpmi to see if it will works better: no luck urpmi downloads everything then I get "Installation failed" the file "XXX.rpm" doesn't exist even if I see that the file was previously downloaded! Aaaarrrggg...

    I can probably fix all these problem, but it is going to cost me a lot of time and I'm tired of always fixing something in the Linux/Mandrake configuration.. Maybe I'm ready for Debian..

  • In my oppinion:
    Yes

    Yes

    Probably

    Yes

    Definately

    --Ben

  • Somehow, I don't feel that "apt vs. urpmi" has gotten as much airtime as the aforementioned conflicts..."

    Personally, I'd like to see the merits and demerits of both listed and "discussed".

  • Let the trolls submit Ask Slashdot questions to inflate the page views. This might actually work!

  • Mandrake has changed ALOT since 6.1... Until 8.0, Mandrake was definitely my Linux distro of choice, but not one I would use regularly on a workstation. Now, with 8.0, everything is there that I need, everything was a piece of cake to get running (easier than Windows, I'd even go so far as to say), and I haven't had to screw with any config files by hand. There's no one that could truthfully say the same for any version of Debian. Maybe Debian is a little more flexible on some things and not quite as desktop-oriented as Mandrake, but it is certainly light years behind Mandrake in the ease and usability department.
  • ok, debian didnt ship it, but they allowed it to be distributed:

    http://lists.debian.org/debian-user-0106/msg03510. html [debian.org]
  • "Urpmi is less succeptable to broken dependancies than apt-get is, due to better design."

    I have to disagree. Each is only as good as the packages being installed. Why? Because the package provides the dependancy info.

    If you use apt-get and have dependancy trouble it's likely that your packages are sh*t. If you use apt-get to install and manage official debian packages you will rarely encounter trouble. I have maintained a debian box with apt-get for going on 4 years, doing monthly "apt-get upgrade" and "apt-get dist-upgrade" sessions that have carried it from Debian version 2.0 through 2.3(unstable) through the years with no reinstall.

    It's the package maintainers who ultimately determine how well it works because it's the dependency info in the packages that make or break your experience.

    -Ben
  • You learn something new everyday. As a former Debian user, I was getting pretty pissed off at having to manually install dependencies with RPM all the time. I'd don't at all like the slow and ugly GTK+ interface, I'm a KDE/command line person, and I uninstalled all that stuff. Now I learn about this "urpmi" thingy and I must say I'm red in face thinking about all the time that I've wasted with rpm. Holy cripes, why doesn't Mandrake inform its users better? Everybody knows about Debian apt-get, Debian advocates never fail to mention it, yet I've never ever heard of urpmi until now. What is wrong with this picture? Yet Another Clueless Bastard
  • Don't forget:

    Is LEGO better than K'Nex?

  • I am a former Mandrake user who switched to Debian.

    urpmi works great to install a new package. But I never got it to upgrade the distribution. Going from Mandrake 7.0 to Mandrake 7.1 for example, was always very complicated. It was not working right when I added different repository, like the kde newest version.

    I never had those problems with Debian. I started with potato and upgraded to woody with no pain at all. Not even a reboot. I now have the freashed kde available and it is very easy to keep up with what is new.

    Thought I may have been a poor user of urpmi, it's lake of upgrade capability was the key in my decision to switch.

  • It used to be nice, but I haven't been able to get it to work on any of the three machines I have Linux on, since somewhere around the 7.1 release.

    Possibly there is a curse.
  • by spongman ( 182339 ) on Thursday June 28, 2001 @02:27PM (#121575)
    I use apt-get and dselect on my debian system, and it's a dream. I remember installing slackware from scratch back in '93 - upgrading linux has certainly come a long way.

    I guess you should probably use the package installer that's native to the distribution you're using. That way you can be sure to get all the right bits, with the correct libs, etc...

    The good thing with debian is that almost everything you're likely to need is right there on their servers, you don't have to go and find the packages on some server somewhere. For example I wanted to install apache and squid last week, I typed one command, it downloaded all the stuff, and within a minute or two of waiting for the downloads (I didn't have to type anything) both were configured and running. If your system is also that easy, then stick with it.

  • in the 97 linuxexpo, during the paintball editor wars, against the vi team. i guess that settles once and for all, which one is better. emacs = lousy shooters, slow, wouldn't move at all. vi = small, fast, running around = we got emacs team. :)
  • It is no wonder we take so long to get anywhere. How can you have an innovation race if no-one can agree who is winning? Maybe, just maybe, if there was something to drive the development forward you would see clear and notable distinctions between these rival formats/packages.
  • Sadly, I found when I was on a Debian system for quite awhile that Debian never issued updates for their versions. I had a production system that had to be RedHat because I needed to know that I could easily retrieve the updated packages and plug them in without breaking package dependancies. I couldn't do that on Debian from 2.0 through 2.2, just before which I switched at home from Debian to RedHat. Simply put, waiting over a year for a package to get updated on stable isn't realistic, and I could not put a version labeled 'Unstable' on a production server - my boss would have had my head on a platter for it.
  • Good grief. He even hand-fed you the fact that it was satire, and you still didn't get it.
  • urpmi has been useless for me on both of my Mandrake 8 boxen, after about a week's worth of casual use. (It dies in some sort of a perl dependency, to be specific.) Consequently, rpmdrake is also hosed.

    I'm not the only one, either... check out the horror stories on MandrakeForum [mandrakeforum.org].

    On the bright side, rpmdrake is the first well-designed GUI package manager that I have laid eyes on. When it works, it works well. I hope they iron out the bugs for mdk 8.1.

  • Hmm.

    Moderators: I _hope_ you see the satire.

    Yet this comment gets moderated as Informative, and Insightful. Makes you wonder if the moderators even bother to read the articles.

  • Do people really use apt-get directly instead of dselect? Why?
    --
  • by _Mustang ( 96904 ) on Thursday June 28, 2001 @02:41PM (#121586)
    With apt, you not only get your package dependencies solved along with the latest software, you get the work that was put in to making Debian a coherent system that adheres to the Debian policy.

    But isn't that what the whole concept of "distribution" was supposed to mean? After all, what makes or breaks the operating system isn't necessarily how good _it_ is, but how well it "enables" the use of the software that is used for *task*.

    On that note, while I really think apt is killer I also agree that the true success behind it is the work done by the package maintainers.
    Flame me all you want but I think what's really needed is some definitive standard for packages similar to the Win-world Installshield idea. There should be some way for the install routine (make install?) to check some DB (linux has a few of those around, right?) and see if a particular app is installed and where. Think the windows registry but for info purposes only so that the install can be more efficient. This would allow me to automate the use *.deb, *.rpm or compile my own and still keep track of apps and dependencies..
  • by Eslyjah ( 245320 ) on Thursday June 28, 2001 @02:41PM (#121587)
    one thing that turned me off from mandrake is the fact that they tinker with their rpms a lot. things get installed all over the place. you can't (or at least they recommend that you don't) use redhat rpms because they are not "optimized" for mandrake, which i think means that they don't have things shuffled around in them. the net result for me is that i would get confused because all documentation on the internet would tell me to do something and then i would try it and it wouldn't work...because those instructions don't apply to the special mandrake packages. debian is more standardized, and therefore, if i have trouble with configuration or what-not, i can just run a google search and learn how to fix it. for me personally, this is a huge plus not just for the apt-get system, but for debian as a whole.
  • "Show stopper" bugs, security holes, etc. are always backported to the stable build tree. Adding security.debian.org to your sources.list and running a cron job that 'apt-get update's daily for you will solve that problem.

    It's been my experience that bugfixes and security hole plugs are published in the stable tree before I even get e-mails about them from various security lists.

    Trust in Debian. Debian is your friend.

  • Well, there was quite a long time (up until today, in fact!) that I thought of the Slashdot population as a very open-minded community who preferred to let the world know what the best product was, not the one that best suited their politics. However, my faith has been shaken today.

    While I would have to agree with the crowds of Debian users here that apt-get is indeed a superior tool to whatever Mandrake is using these days, I would have to disagree on the ultimate choice of best software package management system.

    Now, Linux is a great operating system in general, and I love the apt-get part of Debian in particular, but why does it have to be on the command line? I hardly think that the average person, say, my grandfather, for example, would be able to deal with learning all the arcane aspects of a command line utility. To most, it is just too frustrating, poorly documented, and complicated. What we really need in a modern operating system is a package manager that the average Joe or my grandfather could use.

    Why hasn't anyone mentioned Windows Update yet? Not only is it a fully graphical tool, but it automatically detects what software your computer needs, without sending that information to a third party, and then gives you an easy install wizard to update everything. Sure, some things may require a reboot, but there is a lot of Linux software that also requires a reboot to function properly. Personally, I think it is a far superior tool to apt-get, because it can also make recommendations on what kind of cool new screen saver you might want to check out, or update DirectX to improve your gaming framerates and such.

    And, of course, it is very handy for patching all those security holes that invariably pop up in MS software, such as the notorious Outlook holes that have caused more than one system administrator a headache. Think about it, if an update tool is easy enough for the average user to utilize, then we won't have to worry about upgrading everyone's Linux machines when the latest BIND or Sendmail exploit hits Bugtraq. It would greatly improve the image of Open Source software when no one goes on a massive hacking spree and compromises a ton of machines for their DDoS wars.

  • by Mike Buddha ( 10734 ) on Thursday June 28, 2001 @02:54PM (#121594)
    But who is the culprit urpmi or the packages?
    It's hard to tell!


    Urpmi is just a transport mechanism. If your system is unstable, then it's the unstable software you installed causing you grief. If the packages downloaded from the site correctly and installed, then URPMI did it's job.

  • I agree completely. I bitched about that same thing in a thread in another article a while back, pointing out that the version of sendmail that ships with stable is older than sand and the version of postgresql is the horrific 6.5 and that Debian required quite a bit of tarballing as a result of the ancient versions of the software represented by the packages in stable, but not surprisingly enough my post was modded down as "troll". Obviously by some clueless individual who doesn't understand that the debianized sendmail segfaults under high loads due to a problem that was long since fixed in the 11.x sendmail series. It's essentially the same thing with postgresql, 6.5 is an unstable piece of crap, 7.1 is an incredible RDBMS. But me pointing out this and providing facts somehow constituted a "troll".

    maru
  • Slashdot.org today announced their latest Internet portal EverythingSlashdot.org which will focus on answering the legalities of everything digitial.

    The strange thing about your comment is that everything.slashdot.org [slashdot.org] actually exists. It's an online information database written and edited by the world. And yes, it has a good writeup about DMCA and the politics of copy protection [everything2.com].

    But be warned: The quality standards on Everything are MUCH higher than on Slashdot. In fact, E2 and Slashdot could hardly be more different [everything2.com].

  • by dbarclay10 ( 70443 ) on Thursday June 28, 2001 @03:04PM (#121602)
    Hehehe :) Well, at least part of your problem was unfamiliarity with the system you were using.

    Firstly, there are currently three different official Debians:

    Potato; this is the stable variant. Just like you described, very little is updated. If it has BIND 8.2.3, and a security hole is found, but a fix is only available in BIND 9, then it'll be backported to 8.2.3. You might think that's absurd. But in Debian, "stable" means that things won't change out from underneath you. Read on.

    Woody; this is the "testing" variant. New packages are uploaded daily, and already-existing packages are upgraded. Packages in Woody have been around for a while, so you should have no problems. However, this isn't "stable", so don't expect everything to be absolutely perfect all the time no matter what.

    Sid; this is the "unstable" variant. When an updated package is available, it goes here before it goes anywhere else. Eventually, it'll move into Woody, but not before it's been tested well. Personally, I find Sid about as stable as most end-user Red Hat boxes. However, accidents do happen, and you should *NOT* run Sid unless you know how to fix things. Yes, this includes having a boot/root rescue diskette, and knowing how to use it. :)

    Now, if you run a server, you should run Potato. That's what it's meant for. But you need BIND 9? XFree86 4.x? No problem, there are several options. The first is to add a "deb-src" line pointing to Sid or Woody, in /etc/apt/sources.list . Then just 'apt-get -b source bind' or 'apt-get -b source xfree86'. That will download the source, (attempt) to compile it, and then give you .debs, ready for safe(ish) installation.

    The other option is to get unoffical .debs. Many package maintainers will compile their packages for Potato, and place them in their home directory on http://people.debian.org for Potato users to download and install. For instance, XFree86 4.x for Potato is available at http://people.debian.org/~cpbotha/. Perl 5.6, and all the Debian build tools are also available. KDE2 packages are available from http://debian.kdyc.com . You get the idea. These are, of course, unofficial packages. So don't expect everything to work perfectly.

    Frankly, if you're running a server, you probably shouldn't be using the latest version of BIND or Sendmail or Apache or whatever. You should probably be running a version that's older and more "secure". Like I said, any security fixes are backported to the version that's in Potato, and are installed when you 'apt-get update && apt-get upgrade'.

    Have a good day :)

    Barclay family motto:
    Aut agere aut mori.
    (Either action or death.)
  • by deno ( 814 )
    Yes there is: MandrakeFreq [mandrakeforum.com] is a semi-stable release of Mandrake-Linux for folks who want to have the newest stuff, but do not dear installing cooker.
  • "urpmi" wins, hands down. It sounds like what a gassy baby would say if it could talk.

    --

  • What you're complaining about is Debian's extraordinarily long release cycles and its notoriously old packages when any given Debian distro is finally released. However, there are some extenuating circumstances you've failed to mention or notice (I honestly don't know which).

    • The old package problem you're complaining about--while not entirely solved--is improving. Debian had some problems during the transition from slink to potato which led to the amazingly long gestation of potato.
    • Stable Debian packages aren't regularly replaced by the latest versions, but this does not mean that Debian packages are necessarily out of date. Debian always backports security fixes to the current stable release. Debian's focus is stability and solidity, not bleeding-edge compliance with the latest versions of all possible packages.
    • Debian is tested as a complete distribution, which is one of the reasons why stable remains locked into older package versions. It's not feasible to retest the entire distribution every time a new revision of emacs is released. When Debian ships a stable release, you can be largely certain that it's one of the most stable OSes you'll ever run.
    • Debian has added the testing archive for folks who want more recent packages than what's shipping in stable, but who aren't willing to live with the occasional broken dependency you find in unstable.
    • The Debian freeze process has been changed. To ensure fresher packages ship with woody when it's released, the most dynamic packages will be frozen last. This should allow users to have reasonably recent versions of important packages.
    • Recent versions of apt allow you to pick and choose among the three archives (stable, testing and unstable). Need the absolute latest version of Mozilla? Apt-get it from unstable. Debian hasn't tested your distribution with that version, but that doesn't mean you'll suffer unnecessarily. I ran 2.2 kernels in slink forever and I don't think slink was ever certified with 2.2.x kernels.
    • You'll always have the ability to download a tarball and roll your own Debianized package for whatever you need. You can't apt-get tarball yet, but I wouldn't be surprised if somebody adds that functionality to apt someday.

    Overall, I think Debian's package-management system is excellent. It only took one ill-fated attempt to add XFree86 to a Red Hat machine to convince me that rpm's file-based dependencies are inferior to dpkg's package-based dependencies.

  • by Bob_Robertson ( 454888 ) on Thursday June 28, 2001 @03:09PM (#121610) Homepage
    i know the article is about command line apps, what about dselect?

    i've used dselect since my first Debian installation in 1997, which also happened to be my first Linux.

    i like getting a description of the package, being able to key-word search through the descriptions since i don't always already know what something is called.

    surely there is enough room in this idea-space for everyone to use the one they like?

    Bob-

  • by bad-badtz-maru ( 119524 ) on Thursday June 28, 2001 @03:12PM (#121612) Homepage

    apt-get only gets the packages, dpkg is the package management utility, dselect is a front end GUI to dpkg. dpkg maintains its database of package stati in /var/lib/dpkg/status and you can use dpkg -L to see what was installed and where. So essentially, the functionality you described already exists.

    maru
  • Is emacs better than vi?
    Yes, but xemacs is better than both.

    Is red better than blue?
    Red is most definately better than blue. You'd have to be a sloped-brow knuckle-dragger if you thought otherwise.

    :P
  • Yup. It's great if you want to quickly install something you know. If I want to browse the newest packages, see what package x recommends installing as well (ie: mozilla-browser recommends mozilla-psm and mozilla-mailnews) I use dselect.

    apt-get is great if you want to quickly install apache for some testing. 'apt-get install apache' [click, wirr] done. Also, if you get to know the package naming formats you can guess that to install mod_perl you'd do an 'apt-get install libapache-mod-perl', or libapache-mod-ssl or whatever.

    I personally prefer dselect for browsing, and apt-get for quick and easy.
  • by Crouchy ( 7129 ) on Thursday June 28, 2001 @03:17PM (#121619)
    Mandrakes own rpm packer RPMDrake in version 8.0, not because I wanted to but because the command line rpm didn't work, I can say it lacks some good features.


    I was installing mandrake 8.0 last night, and managed to stuff up the config file for cups and my simple solution was to reload the rpm.. Or I thought it was, RPMDrake refused to delete the package (hanged big time) and there is no option to install over a corrupt file. The problem with this package was it lacked lots of features that the command line rpm has. So I downloaded the tar file from rpm.org and got a working version.


    My experiences with debian (some what limited), is that sure it doesn't have all the nice GUI (or at least when I used it), but it works. I loved how it would automatically download the dependencies, and do a bloody good job.


    I do like the mandrake package otherwise, such as there flashy splash screen whilst starting up.

  • - Apt has libraries to ease the life of anyone who wants to create front-ends. As a result you have:
    - Gnome-apt
    - aptitude
    - console-apt
    - etc. etc. etc
    (Check on your facts)
    Apt has many front-ends, mostly on the text screen, but 'graphic' and useful.

    Debian isn't targetting the average Joe Schmoe, or at least not in its current status.

    Windows Update is not even comparable to apt-get, because it only updates a very small subset of the installed software. In Windows, every piece of software has its own code to update itself from the web (Except MS software, perhaps).
    Windows Update does not handle libraries upgrades/etc as well as apt-get, because Windows hardly has any package management for installed libraries (apart from that useless registry list of DLL's) at all, not to mention any other shared files/resources.

    In summary, Windows Update may be useful to upgrade those 4 or 5 apps you mainly use, but apt-get can upgrade any one of the ~7000 packages you potentially install (Due to conflicts, its actually probably a ~1000 less than that).
    Apt-get has libraries allowing easy creation of front-ends, and various ones already exist.

    Get a clue.
  • by Ramses0 ( 63476 ) on Thursday June 28, 2001 @03:26PM (#121624)
    100% agreement on the previous comment. All packages on debian must adhere to policy [debian.org], which is not overbearing, but rational and well thought out. Plus since all packages in debian *must* follow policy, what you learn for one package applies directly to every other package on the system.

    Part of policy is that every program must have a man page, which was very nice when I was first learning to use linux.

    I have always had very good results from mailing the maintainers of packages. So far, I've traded emails with the maintainers of: xawtv, makedev, php4, gabber, and xserver-common (who in some cases were also the developers of the packages in question, not including miscellaneous bug reports).

    I've only had to mail maintainers since I've been using the 'unstable' distribution (which has only crashed once), and it's usually just been a heads up that some library upgrade broke some other function that their code depended on. This is not a problem when dealing with the stable distribution because it does not change.

    Before that, I was able to get all the help I needed from the debian IRC channels (all IRC programs come defaulted to the debian irc servers, another nice touch).

    I'm sure that once I mail my latest buglet report to the maintainer of icecast-server (program is compiled with crypted password support, but configuration files default to storing non-crypted passwords) that it will be responded to promptly, and integrated into the next update of icecast.

    One final bit of debian evangalization: debian (almost) invented the word Free (with a capital 'f') when talking about Free/Open/GPL software [debian.org]. All programs distributed with debian must allow redistribution, must come with source code, and must allow modification of that source code. (well, mostly- some exceptions apply). This means that I *OWN* all the software on my computer in a way that's ten times more real than any software that I've paid for (just so long as I'm willing to share).

    Lest you think that debian is all a bed of roses, not all programs are up to date, packages are maintained based on whether somebody is interested or not. Sometimes the developer of one program will break other programs unless versions are kept relatively in-sync. And finally, since you didn't pay for it, you can't really complain to anyone when there is a problem. The only solution is to revert and/or retry.

    All in all, I am very pleased with debian, it does it's job quietly, and does it well.

    --Robert

  • Why hasn't anyone mentioned Windows Update yet? Not only is it a fully graphical tool, but it automatically detects what software your computer needs, without sending that information to a third party, and then gives you an easy install wizard to update everything. Sure, some things may require a reboot, but there is a lot of Linux software that also requires a reboot to function properly. Personally, I think it is a far superior tool to apt-get, because it can also make recommendations on what kind of cool new screen saver you might want to check out, or update DirectX to improve your gaming framerates and such.

    A Few points...

    • People have already mentioned Windows Update
    • Neither apt-get nor urpmi submit information to a third party (unless you count the hits that the file downloads cause -- but then both apt-get and urpmi download files from various mirrors. Windows Update, unless I am mistaken, all comes from Microsoft...)
    • Yes, there's a lot of software that requires a reboot while using Linux distribution. I'll summarize it in three words: The Linux Kernel. That's right, the only reason you'd have to reboot your computer is to upgrade the kernel. Name another "reason", and I bet you can do that just fine in userland without rebooting.
    • Windows Update tends to break things, and your box is sometimes rendered useless.
    • Windows Update doesn't really sort out dependancies; it just knows what you can and can not install at the same time. It does not take care to do what you say; you have to do things the way it dictates.
    • You can not download 3rd party software or provide a configuration option for any outside sources within Windows Update.

    Anyway, enough diversions. I'm going back to reinstalling Debian a machine that was once running Mandrake for a while. "urpmi", although nice, didn't hold a candle to "apt-get" -- and this is precisely the reason I'm switching the distro back. Mandrake's stuff does have an easy enough graphical frontend, however.

    Really quick, however... my largest complaints with urpmi are, as follows:

    • One must download an ~8M description file from a single server
    • The dependancy handling isn't done as well as under Debian
    • Error messages under urpmi aren't as helpful or descriptive as those of apt-get
    • You cannot define your own multiple sources as easily with urmi as you can with apt-get
    • When paths of software or various other somewhat important things occur, it does not optionally notify you like apt-get can
    • Since it takes a long time to download and parse the large file (see above), urpmi was noticably slower, especially in the GUI when it had to refill lists and trees.

    For what it's worth, console-apt (and using apt-get by itself too, of course) usually suffices for me, but I would love to see a useable GTK+ based frontend for Debian's package system one of these days. I think a lot of other people would like that as well.

    If we had the concepts of Red Carpet, the slickness of Windows Update, the widespread use of urpmi, and the power of apt-get all rolled into one tool, it would truly be the killer upgrade apt -- err -- I mean app. (:

  • by Ted V ( 67691 ) on Thursday June 28, 2001 @03:34PM (#121632) Homepage
    A history of the eternal battle of red versus blue, in different contexts.

    Monty Python and the Holy Grail:
    "Red! No, blue! Aaaaahhhh!"

    Red: 1, Blue: 0

    The Matrix:
    "Take the Blue pill and you wake up and believe whatever you want to believe. Take the Red pill and I show you how deep the rabbit hole goes."

    Red: 2, Blue: 0

    Pokemon:
    Charizard, a fire pokemon, is weak to Blastoise, a water pokemon

    Red: 2, Blue: 1

    Google:
    Searches for "red": 23.6 million
    Searches for "blue": 17.3 million

    Red: 3, Blue: 1

    Cold War:
    Red = Commie Bastards!
    Blue = Good Americans!

    Red: 3, Blue: 2

    It seems that Red has still eaked out a narrow win over blue... For this time!

    -Ted
  • That's correct. If you have testing it the sources list it would update it. The feature isn't in potatos apt(ironically enough), but the newer version should allow you to selectivly upload to packages in testing or unstable. The big problem is that core libraries of often upgraded to versions incompatible with the libraries in stable
  • I have put all of my system packages on "hold" , so they do not get changed at all. Then if I want something new and improved, like galeon, I just hit `+' in dselect to select galeon, and it shows me a list of packages which I would have to upgrade if I want galeon. I inspect it and decide whether to unhold them or not. Easy.

    Regard,

    Zooko

  • It only took one ill-fated attempt to add XFree86 to a Red Hat machine to convince me that rpm's file-based dependencies are inferior to dpkg's package-based dependencies.

    Your problem is with RedHat's(and other's) packages. RPM allows you to use package based dependencies, the difference is that RPM will automatically do file based dependencies if you don't specify a package that satisfies that dependency. It really seems to be more a problem with the tools for packaging than the RPM format as such.

  • "Red! No, blue! Aaaaahhhh!"

    Actually, he said blue, then yellow.

    Another red and blue: the boxes in "Time's Rub" by Greg Benford. No clear preference though.

  • As root:

    1) su
    - type in password
    2) echo "0 6 * * * root apt-get update && apt-get upgrade" >> /etc/crontab

    And you'll always get the updates.

    As other people said, I've never HEARD of urpmi. There's one thing I have to give Mandrake credit, though - I learned linux off of that distrib, but that was after I was too confused on Debian's SETUP, not apt-get (that too, considering I was only on dialup, and I didn't download their CD images because I couldn't find it, being the linux-newbie I was. Cable made the difference)
  • You're right. Debians main advantage (in terms of packaging - I prefer Red Hat for other reasons) seems to be in uniformity between packages. I.e.

    * Package granularity. Is libmng part of qt, or packaged seperately?
    * Naming conventions. mod_php? mod_php3? apache_mod_php3? apache-mod-php? Each distribution wishes to call these things by a different name.

    * Inconsistent or bad dependencies. Apps depend on SDL = 1.20 when they should probably depend on SDL >= 1.20

    * Mutual dependencies. A needs B, B needs A. You can install them simultaneously to get around the problem, but logically it seems a little odd.

    * Versioning conventions. Applications distributed both as numerical

    Basically its a management issue. There's easily far more RPMs out there than the 6 gig in the main Debian archive, but lack of management causes inconsisteny, which leads to headaches installing apps.

    That being said, apt-get was written from the ground up with dpkg in mind.

    Are you sure of that? I seem to recall the apt-get team saying that the exact opposite was the case - the system was specifically designed to packaging system independent.
  • Don't listen to what other people have replied :)

    Anyways, you're partially correct. If you want to run Potato, don't put a Woody or Sid "deb" line in /etc/apt/sources.list . Putting a Woody or Sid "deb" line into your sources.list to get just one or two packages is fairly dangerous.

    But I wasn't talking about a "deb" line :) Just a "deb-src" line. 'apt-get install', 'apt-get upgrade', and those, use "deb" lines. 'apt-get source', 'apt-get -b source', and those use "deb-src" lines. :)

    Now, 'apt-get' always gets the newest version of a package available, *if* a newer version is available. It won't replace what you have on your drive with and older version. Simple as that :)

    Have fun ;)

    Barclay family motto:
    Aut agere aut mori.
    (Either action or death.)
  • by deno ( 814 ) on Thursday June 28, 2001 @04:09PM (#121658) Homepage
    First, Mandrake distros (with exception of "corporate server" and "MandrakeSecurity", which target different public) are always extremly up-to-date, while debian takes forever to issue a new distribution.
    Obviously, slower developement cyclus means that there is more time to take care of details... Unfortunate side-efect is that many "stable" debian packages tend to be very obsolete.

    Second, there is no such thing as third-party debian package, while third-party rpm packages are abundant. Quite obviously, updating a system with tons of third-party packages is a rather difficult task.

    Third, average debian user is far more knowledgable than average Mandrake user. (He has to be, simply because getting a debian system up and running is by far more difficult than doing the same thing with Linux-Mandrake.) Therefore, things which some Mandrake user reports as "evil mandrake stuff" (like: I installed some cooker packages, had to force the install, because it kept requiring some "dependencies", and guess what? now my system is broken!!!) would never be reported as such by debian users.

    There is more, but I think you got the message: things aren't as simple as they look from a high debian-guru ivory tower. ;-)

    As for apt-get and urpmi question, things ARE rather simple: urpmi is better than apt if you use Mandrake distro, simply because Mandrake distro and urpmi were built with each-other in mind. I can think of only two cases when using apt-get on mandrake distro makes sense:

    1) ex-debianers which are familiar with apt will obviously prefer to use the known tool
    2) urpmi (and co.) make a local database of all rpm repositories, and updating the DB takes some time. Therefore, apt may be a better tool for people who often update their systems using cooker rpms. (this may have been adressed already, I haven't checked lately.

    In case you use Debian, there is no urpmi, so apt is definitively better. .-) And.. do not bother porting urpmi to debian - it will be just as useless there, as apt is on a Mandrake system.
  • by Local Loop ( 55555 ) on Thursday June 28, 2001 @04:19PM (#121662)

    The real question is not "which package system is better?", but "which distribution does the best job of managing their releases and updates?"

    I don't care what system they use - my priorities (aside from correctness issues) are:

    • Do they keep dependencies at a minimum?
      I don't want to install 30 packages just to get PHP working. And why does every single Red Hat app seem to require Apache (RPM) and PHP (RPM)?
    • Do they keep library versions well syncronized with available apps?
      And avoid requiring ancient versions of, say, zlib, that won't play well with newer apps.
    • Is the auto update tool easy to use?
      That is, does it present dependencies clearly and show you release notes and advisories. I'd like to know *why* Apache has been updated, so I know if it really affects me.
    • Can I depend on the vendor to quickly release security critical updates
      If I have to resort to source in an emergency, it defeats the whole point of packaging.

    By the way, I'm a huge fan of source installs for apps, becuase I find them much easy to configure and upgrade than packages. But I'd love to use RPMS if it were practical.

    -Loopy

  • Don't you think "broken at heart" is a bit strong for describing a broken install process?


    Setting up the network is a part of the install process. Debian's install sucks. Mandrakes is way better. Nobody denies that.


    But with a .deb system you should only really need to re-install every ten years or so...

  • When I was running Mandrake Cooker, I knew quite a few people who had to frequently start from scratch and re-install. Then there were those of us who used apt-get. ;-)

  • # apt-get update
    # apt-get [upgrade | dist-upgrade]

    I've now upgraded the entire system from debian 2.1 to debian 2.2.

    That's why you use apt-get.

    bendy
  • by blakestah ( 91866 ) <blakestah@gmail.com> on Thursday June 28, 2001 @04:23PM (#121668) Homepage
    For those not in the know on Debian:

    Stable: security upgrades and other REALLY solid upgrades only. You are expected to perform a dist upgrade from time to time because otherwise you will have really old packages. However, NOTHING EVER BREAKS EVER.

    Testing: You get reasonably well tested updates and security updates. Your box is cutting edge. Things still don't seem to break ever, but notice ever is not capitalized anymore. This is more stable than any other distribution's stable.

    Unstable: Not just cutting edge, bleeding edge. Perl may break. Dpkg may break. But mostly things will still hum along, with an occasional hiccup. Power users will want unstable on their workstations - not on production servers. This now has recent mozilla, konqueror, kword, gnumeric, and other production apps that are changing reasonably fast right now.
  • Now, Linux is a great operating system in general, and I love the apt-get part of Debian in particular, but why does it have to be on the command line? I hardly think that the average person, say, my grandfather, for example, would be able to deal with learning all the arcane aspects of a command line utility. To most, it is just too frustrating, poorly documented, and complicated. What we really need in a modern operating system is a package manager that the average Joe or my grandfather could use.


    This doesn't have anything to do with this I don't think. This is something that probably belongs on an apt list somewhere. I personally like the apt-get command line method, and never use the apt-get-gtk and other graphical wrappers. Besides, the "graphical" way of doing this is called dselect :)

    Why hasn't anyone mentioned Windows Update yet? Not only is it a fully graphical tool, but it automatically detects what software your computer needs, without sending that information to a third party, and then gives you an easy install wizard to update everything.

    See above comment about dselect. Same deal, no info sent to anyone, and while the install "wizard" isn't as pretty looking, it does the job.

    Personally, I think it is a far superior tool to apt-get, because it can also make recommendations on what kind of cool new screen saver you might want to check out, or update DirectX to improve your gaming framerates and such.
    I think this goes back to the "apt-get is not all there is to debian packaging" thread above. apt-get is just a way of interacting with dpkg, and dselect is just a way of interacting with apt-get and dpkg. Your arguments against apt-get are perfectly valid, but they don't hold water when used against the whole packaging management package (if you'll pardon the pun) of apt-get, dpkg, and dselect (and deity, aptitude, apt-get-gtk, etc).
  • i deny that. i personally preffer debian's installer's to mandrakes. if you have a clue what you're doing, the debian install i find much faster, and easier to use to get a minimal system installed.

    but, all personal preferance. i just thought i'd throw it out there that some of us like debian's installer.

    -------

  • What about OpenBSD ports?
    Very cool. Just untar the lasts ports.tgz file into /usr/ports, then navigate through the menus, find what you want, then make && make install. It will go out and fetch the dependancies. Very cool.
  • Actually just "make install" works too... And at least in FreeBSD land, you can update the ports collection via cvsup. No menus there though, it's simply directory navigation. Classic case of doing things the unix way, using the filesystem, using a tool like make the way it was meant to be. And if I need to tweak a port's installation somewhat, I can edit a makefile to do it before even downloading the package. The real beauty of ports is that it compiles everything it downloads, which removes a whole class of problems, namely dependencies on minor library versions because of some piddling format change. Plus you can edit the source or makefile for different options, and "make install" it again, without having to go rebuild a package and hope the patches don't clobber it. Now if I could get that sort of flexibility in apt, this webmaster/sysadmin might actually go to Debian over FreeBSD (as it is, it's my second choice).
    --
  • by scrytch ( 9198 ) <chuck@myrealbox.com> on Thursday June 28, 2001 @05:33PM (#121678)
    Oh yeah, forgot one of my other favorite things about ports: it does dependencies by files, not packages. So if I installed qt by hand, for example, it trusts me to know what I'm doing, and the dependency on qt is satisfied because it actually looks for qt in my library path. Same deal with apxs for apache, perl for perl, etc. The dependency logic can be as complex as you need, because it's all based on make. No need to install "fake" packages, force installations, etc.
    --
  • "Well, there was quite a long time (up until today, in fact!) that I thought of the Slashdot population as a very open-minded community who preferred to let the world know what the best product was, not the one that best suited their politics. However, my faith has been shaken today."

    HAHAHAHAHAHAHA!

    Slashdot has NEVER been an open-minded forom. Slashdot is a haven for Linux and copyleft fanatics. If you consider Slashbotters open-minded, you must consider the Taliban a haven for free-thought.
  • by CoughDropAddict ( 40792 ) on Thursday June 28, 2001 @05:38PM (#121681) Homepage
    i like getting a description of the package

    $ apt-cache show dpkg
    [...]
    Description: Package maintenance system for Debian
    This package contains the programs which handle the installation and
    removal of packages on your system.
    .
    The primary interface for the dpkg suite is the `dselect' program;
    a more low-level and less user-friendly interface is available in
    the form of the `dpkg' command.
    .
    In order to unpack and build Debian source packages you will need to
    install the developers' package `dpkg-dev' as well as this one.


    [I like] being able to key-word search through the descriptions since i don't always already know what something is called.

    $ apt-cache search slashdot
    bk2site - Utility to turn bookmarks into Yahoo/Slashdot like pages
    gnome-applets - Various applets for GNOME panel
    lg-issue38 - Issue 38 of the Linux Gazette.
    libapache-mod-perl - Integration of perl with the Apache web server
    surfraw - a fast unix command line interface to WWW
    ticker - configurable text scroller, with slashdot and freshmeat modules
    wmheadlines - Linux news website headlines integrated to windowmaker's menus


    Some people like dselect (and more power to them!) but I don't even touch it any more...

    --
  • Apt-get can do the same thing that Windows Update does, but with less effort and greater robustness. The command is:

    apt-get dist-upgrade

    ...and thats another thing, what is so difficult and unfriendly about that? Seems pretty damn straight forward to me. How is Windows Update easier than that? Oh, and how much you wanna bet that dist-upgrade does a better job than Windows Update?
  • Yes, there's a lot of software that requires a reboot while using Linux distribution. I'll summarize it in three words: The Linux Kernel. That's right, the only reason you'd have to reboot your computer is to upgrade the kernel. Name another "reason", and I bet you can do that just fine in userland without rebooting.

    "Rebooting" is a red herring. I can obviously switch to run level 1 and do pretty much anything (short of changing the kernel), but I've killed off my computer's functionality. At that point my escape from my BIOS's POST sequence is a little Pyrrhic.

    For instance, if I want to upgrade my X server, I have to kill every (non-console) program I'm using. Yeah, sshd is still up and running, but I don't run a server box, I run a workstation, so I could really care less.(If your box is primarily a network server, you're not upgrading the X server anyway; you're upgrading some network service, and the loss of *relevant* functionality is similar. I tend to segregate my servers from my workstations; if you just have one machine doing it all you might appreciate the fact that your friends can still download your mp3s while your productivity drops to zero.)

    This is similar to how kids claim that their super-stable Linux box has enjoyed 14 months of uptime while their Windows box crashes weekly. Maybe so, but if your window manager or web browser crashes three times a day under Linux (not too unlikely), it has a lot more of a negative impact on your productivity and pisses you off a lot more than having to sit through a POST once in a while.

    I obviously agree that Linux is lightyears ahead of Windows in terms of the granularity of service disruptions imposed on you by upgrades. I just wanted to rant a little ;)

  • But people also run LInux and BSD without running X at all .. so would you say that they are essentiall y working on a system which isnt turned on ?


    Just a reminder to all :
  • Why? Why must this be so? Linux is not an OS unto itself, only the foundation of one. Why can we not make room for the different ways people work? Why must it always be one "right" way, and everything else is wrong?

    I like Debian. I might give friends who use Mandrake or RH some shit for doing so, but in the end, it's their choice. Debian is my choice. Why must choice be bad?

    Oh yeah - the Windows users who can't make a choice, and don't understand anything about what they're doing. I don't know about you, but I've found what I like, and everyone else should be able to choose as well, not have the "one true way" shoved down their throats.
    _____

    Sam: "That was needlessly cryptic."
  • Do people really use apt-get directly instead of dselect?
    In short: I hope not. Apt-get is really only useful after an initial dselect. If you're using apt-get dist-upgrade, only pacakges you currently have (dpkg --list if you're curious) will be upgraded, and packages will be added or removed based upon the dependencies of said packages. If you have nothing installed on your machine, apt-get is useless unless you know every single package which is necessary to get the base system up and functional.

    That's where dselect comes in. You need dselect to select the initial packages for your box (due to its default package list, etc.). But after that initial dselect, you never really need to touch dselect again, apt-get takes care of it all.

    So, to answer your question [at least from my experience], people use dselect initially to configure their box, and then apt-get to maintain it after the fact.

    In addition, what I've learned to do is use dselect as a tool for searching for obscure packages I need (but don't remember the package name, etc.), and then just apt-get install packagename. Apt-get can't replace dselect in that functionality (although you *could* grep through the apt-get package lists if you felt like it, and I have), but there is really no point to running dselect after the initial install to maintain pacakges.

    On the other hand, if apt-get were included on boot/rescue disks, and apt-get base_install were possible [or dinstall used a nasty apt-get instead of a clean dselect], then dselect would lose much of its standing and apt-get could eventually completely replace dselect. I, for one, hope both dselect and apt-get stay around for a long time, together, they're incredibly powerful and helpful.

    ---

  • (my attempt at writing a childish troll)

    NeXT File bundles rule, packages drool. Friends don't let friends reinvent the M$ registry.

    (troll complete. awaiting negative karma)
  • I think that the question should be 'do people really use dselect?' Because dselect is quite awful program to use. It has very complicated user interface with weird logic.

    Besides there is also better alternatives to those who doesn't like to use commandline apt-get. For example gnome-apt and console-apt.

    I personally use only apt-get.
  • Ok, that PAM problem was found in Sid (unstable!!), so, from my point of view, if you install an unstable branch, you agree that you might have that kind of problem ..

    Anyway: reboot, single mode, login, lynx incoming.debian.org, get packages, dpkg -i *.deb, reboot =)

  • What I've found the coolest part in OPenBSD's ports(and probably also NetBSD pkgsrc/FreeBSD ports, though haven't tried) is that you can go in and set all kinds of options in the Makefile before you do make && make install.. for example, I was very pleasantly surprised for all the options available in the PHP4 port. No more juggling around hopelessly with binary packages when I sometimes want gd, mysql, imap, ldap and blahblah modules built into my PHP.. I just set that these are the things I want, then it fetches everything it needs, and builds them. Very nice.
  • by Cardinal ( 311 ) on Thursday June 28, 2001 @11:21PM (#121718)
    Second, there is no such thing as third-party debian package, while third-party rpm packages are abundant.

    Of course there are third party Debian packages. I see project sites all the time these days offering their own deb packages. Additionally (and even better) they offer their own apt-get URLs for people who wish to use their third-party Debian packages. Currently, my sources.list includes three such lines. One for E17, one for efm, and one for gabber.

    Third-party packages was also the only way to get KDE packaged for Debian until it was finally included.

    Now of course, they will not be nearly as abundant as RPMs simply because of the number of RPM-based distros out there, and the ease of making RPMs as opposed to DEBs. But they are there, even if there isn't a debfind.net yet :)
  • Between 7.2 and 8.0 Mandrake switched to a newer version of the glibc (2.2, I think). As a rsult, all of their binary rpms now require that version of the glibc to run.

    I've been unable to upgrade from the previous glibc to the more recent one with the rpm system. I've also been quite surprised to see that the two versions of the glibc files actually share the same name (libc.so.6).

    As a resultt, I can't install Mozilla 9.1 as a binary rpm. I could probably compile from source, but I think that rpms were created exactly to avoid doing that !

    Does Apt-Get work better in that regard ?

    Thomas Miconi
  • I switched from Mandrake to Debian about a year ago. I switched my baby laptop [toshiba.com] first - having funny hardware and no floppy drive it's always a pain to get a new distro on to it, but Debian was extremely easy. And I got blown away by how slick dselect [debian.org] was (yes, I know hard core Debian users are snobby about dselect and prefer command-line apt commands; but dselect still hugely impresses me with how good it is).

    Then I went to upgrade my desktop box to Mandrake 7.2, and the install just croaked, repeatedly. It just would not load on my SMP, all SCSI machine. After two days of messing about without any success, I just got pissed off with it. Mandrake seemed to me to have put all the effort into surface glitz while ignoring the underlying engineering. Then I stuck a Debian CD into the drive, and it just booted, loaded, and ran, and I've never looked back.

    I don't want glitzy GUI interfaces; I want solid engineering that works every day. Although I've been bitten a couple of times with Debian 'unstable' and now stick to 'testing', I'm still hugely impressed with the overall feeling of solid quality with Debian. All my new servers this year are Debian (most of my older servers are still Mandrake, because they are working and there hasn't - yet - been any need to reinstall them).

    Mandrake and the other commercial distributions, like AIX and Solaris and SCO, are essentially maintained by small groups of people working for pay to targets and deadlines set by masrketing. Debian, like Linux, is maintained by a large group of people working for the fun of it to deadlines they set themselves. I believe that the reason Debian is better than Mandrake is the same as the reason Linux is better than AIX and Solaris (yes, I have AIX and Solaris boxes too): fun is a better motivator than pay.

  • Setting up the network is a part of the install process. Debian's install sucks. Mandrakes is way better. Nobody denies that.

    I deny it.

    Mandrake 7.2 (haven't tried 8) won't install on three of my nine Linux boxes - at all. 33% failure rate. Different reasons, but essentially if you have interesting or unusual hardware Mandrake install just doesn't want to know. Debian installs without problems on every one of my boxes. Mandrake's install sucks. Debian's install is way better.

  • Here's my only tit to pick:

    Think the windows registry but for info purposes only so that the install can be more efficient.

    The Windows Registry is only for "info purposes". There's no code there, although you could add it in theory. Code is also data, so everything we do with computers is really for "info purposes" ;-)

    What is bad with the Windows Registry is its backup routines (it actually backups at each shutdown I think), lack of decent dependency, consistency and integrity rules and checking, lack of good overview by the user, cryptic keys, too many independent systems within it and too much unnecessary spam already inserted into. In effect the user may be be held hostage by a huge and incomprehensible database that might be corrupted in one way or another.

    You've a good idea though, but it's already there in Debian I believe. Unfortunately having many distros means some incompatibility, no matter what.

    - Steeltoe
  • You don't have to change the options in the Makefile you know.

    For OpenBSD's PHP port, just do:

    $ env FLAVOR="imap gettext mysql gd" make install

    and it'll do everything else automagically.

    For a full list of possible flavors, do:

    $ make show VARNAME=FLAVORS

    Different flavor combinations result in a different binary package getting created.
  • Cross-pollination is good. But standards would be better :)

    But then, packages are more than file and archive formats. It's mainly adherence to a set of rules (like Debian Policy - I'm sure each distro has its own set), therefore until there is no agreemenmt on the rules (and maybe never) a common package format and download protocol would be of little help.

    So, I'll settle for cross-pollination.

  • If anyone is having probs getting apt from the mandrake contribs to works, in the file

    /etc/apt/sources.list

    change the line

    rpm ftp://ftp.sunet.se/pub/Linux/distributions/mandrak e-devel/i586 Mandrake cooker

    to

    rpm ftp://ftp.sunet.se/pub/Linux/distributions/mandrak e-devel/cooker/i586 Mandrake cooker
  • Ports is probably my favorite by far. I have run into problems using apt-get to install non-debian hosted packages like KDE. This is an irritation
    for projects that require many packages to be installed.

    Ports is really flexible in where it downloads source code from which is then patched upon download and built locally and installed. It also gets all the dependencies it needs along the way.

    http://www.freshports.org is a good site to watch how many port updates occur each day and all the new ones. Its pretty up to date but that as it does with Debian packages depends on the port/package maintainer.

    Dave
  • My favorite difference (from RedHat RPMs) is the use of the Debian menu system.

    Really? It's my favorite difference too - it's the one that's keeping me from using Mandrake. I can stand the arrogance of distributions that think they have a right to take over my window manager menus when I know damn well where my programs are too. (Not to mention that when you upgrade your wm or desktop by hand, you lose their menus!) In general, distribution menus suck, and distribution icons, color schemes, and wallpapers suck too. (Mandrake looks like it was designed by a four year old with a bunch of crayons).

  • by DrXym ( 126579 ) on Friday June 29, 2001 @06:39AM (#121762)
    MandrakeUpdate is an adequate tool once you get to used it but it is still overly complicated for the novice. Part of the problem is that it offers little assistance to set it up and contains some very cryptic buttons. It would only be by luck that a novice would know that the "Edit Sources" button is what you must click on to add an update site (after filling in the cryptic "New Source" dialog), or that "Reload sources" actually means "Check for updates".

    Why couldn't they give it simple UI like Red Carpet instead of all these cryptic buttons and dialogs? It wouldn't have diminished its usefullness to do so.

    Frankly it's perplexing. An hour in a usability lab would have exposed these flaws. It makes me wonder if Mandrake have any clue about usability at all. It is no wonder people say Linux isn't ready for the desktop when distros can even write a software update tool without slapping an overly complicated UI on top of it.

  • Do they keep dependencies at a minimum?
    The answer is you set dependencies to what the package requires. It's not a "Mandrake hates you so they require 800 packages for php to work" type thing. One guy has even done HUGE research and experimentation to convert apache/php/ldap/imap to a completely modular setup. If you have ever compiled php into apache using source, you know that in order to upgrade one, you must upgrade BOTH (and it's worse if you have imap and ldap in the picture). Mandrake provides mod_* rpms so that these extra functions are completely modular and can be added/removed/upgraded at will. I am unaware if RH offers these same packages. All they have to do is use the spec files from the src rpms.

    Do they keep library versions well syncronized with available apps?
    If you're mixing and matching packages from older distros or other distros, then you will have problems. If it absolutely refuses to install the rpm, grab the .src.rpm and recompile that. There's a great article by the Mandrake gurus on how to make rpm packages [linux-mandrake.com]. You might have to make some minor tweaks to the spec file and/or recreate the patches, but it's definitely easier than building everything from source with all the correct features enabled, and all the ones that cause problems disabled, etc...

    Is the auto update tool easy to use? That is, does it present dependencies clearly and show you release notes and advisories. I'd like to know *why* Apache has been updated, so I know if it really affects me.
    The auto update tool...if you mean something that runs in a cron job like apt-get every night, I think you will be disappointed. But if you mean "select a package from a list of available packages and have it automatically fulfill dependencies either locally or from a defined ftp site", then the answer is yes. As far as *why* apache was updated, I do not think that security issues are normally recorded in the rpm descriptions, but I could be wrong.

    Can I depend on the vendor to quickly release security critical updates. If I have to resort to source in an emergency, it defeats the whole point of packaging.
    There are guys that monitor security aspects as the primary focus of their job. They verify/classify the security reports on places like BugTraq and then upgrade the packages and release them to the mirrors. But you always have the option that I described above. Grab the source, tweak the .spec file, and make your own rpms. It's not that hard. It IS a learning curve, but once you get past that, you'll be rpm'ing your way to the drugstore for more fix.

    Blue skies... Cannonball
  • You are correct, MandrakeUpdate is just a front end to urpmi. Found this out the hard way when I broke urpmi by installing Perl 5.6.1 - you see, urpmi is written in (mostly) Perl and none of it's libraries were moved to the new @INC.

    So, if you're going to upgrade to Perl 5.6.1, make sure you copy the Locale::GetText library, as well as the rpmtools library and the urpmisomething library (can't remember, at work, using Win2K) from your Perl 5.6.0 $EPREFIX/lib/perl5/site_perl/5.6.0/.

    I probably should mention that if urpmi won't work, then MandrakeUpdate won't work at all, but it also won't display any errors which is most annoying.

    --

  • I download the sources from debian, and the latest sources from the real maintainers. Pick through the pkg/debian/ directory, and basicly repackage the app/lib without doing all the work by hand again.

    You should take a look at the "uupdate" program, from the "devscripts" package. It automates this particular step for you (although of course if it's a dbs source or if upstream has changed their build system, you're out of luck)

    Generally, on a stable system, I don't find myself having to do this..it's my experience that the versions in unstable are up-to-date enough unless I have a special need for a particular feature in a new version.

    Daniel

  • Ummm.... I was referring to not having to use the stupid menus at all for programs that aren't in there - it's better than the distro inflicting all sorts of penguin-themed cuteness on me!
  • Because I can browse for packages that I need

    apt-cache search


    Because when I find a package all the information is there about dependencies etc

    apt-cache show


    Because it allows me to preview the dependencies and change my mind if I don't like what they throw up
    apt-get install (yup, it asks)

The Tao is like a glob pattern: used but never used up. It is like the extern void: filled with infinite possibilities.

Working...