Debian Planet

Welcome to Debian Planet


Apt-get into it.
Main Menu

  • Home

  • Topics

  • Web Links

  • Your Account

  • Submit News

  • Stats

  • Top 10

  • Debian

    These are important Debian sites one should not be without!

  • Official Debian site

  • Package search

  • Mailing list archives

  • Bug reports

  • Debian on CD

  • Unofficial woody CD ISOs

  • Unofficial APT sources

  • Developers’ Corner

    Other great Debian news sources:

  • Debian Weekly News

  • Kernel Cousin Debian

    (Debian mailing lists digested)
  • Community Groups

    Need help? You’re not alone on this planet.

  • debianHELP

    (User support site)

  • Debian International



  • EsDebian


  • DebianWorld


  • MaximumDebian


  • DebianUsers


  • Debian-BR


  • IRC

    The place to get help on a Debian problem (after reading docs) or to just chat and chill is #debian on

    Many of the Debian Planet staff live there so pop by and say hello.

    Wanna write?

    Got that latest or greatest scoop? Perhaps you have some important news for the Debian community? Submit a news item!

    Or perhaps you’ve written a rather ground breaking insight into some aspect of Debian and you feel compelled to share it with others? Knock up a longer editorial article and send it to the editors.


    DP is sponsored by Xinit Systems and

    Domains paid for and hosted by

    Buy your Debian merchandise at

    Who’s Online

    There are currently, 74 guest(s) and 2 member(s) that are online.

    You are Anonymous user. You can register for free by clicking here.


    The comments are owned by the poster. We aren’t responsible for their content.

    Re: Novice-friendly updating? (Score: 1)
    by piman on Thursday, December 13 @ 03:03:40 GMT
    (User Info)

    No, I’m quite sure I didn’t mean foster and not orphan. There’s a bug in 1.2.2’s parameters to Feta’s internal run() subroutine, which makes it try to execute multiple commands rather than remove all the packages. The contents command is also pretty broken because of a duplicate push call. Both these bugs are mentioned on the Feta web page, too – I put them there (and I put them in Feta, although not on purpose :P).

    Anyway… If I was a user (which I am), I wouldn’t (don’t) like calling a help desk for information on how to perform a simple task like upgrading or installing software (which is why I greatly prefer APT/dpkg to Windows).

    A console, keyboard-driven file manager, although incredibly useful, is not very novice-friendly. Plus, this still doesn’t solve the problem of integrating all the tools into one simple program it’s easy to teach someone to install something, or list something. It’s harder to teach them to do all those things.

    The primary difference between user documentation and developer documentation is that user documentation is task based, instead of reference based. A user doesn’t want to look through a list of all commands to find “install”, they want to look through a list of what a program can do until they find “Install Packages”. Actually, this contrived example seems stupid, so how about wanting to look up “Making Text Bold” instead of ““. No user is going to guess the second one if they want to do the first one.

    This same principle needs to be applied to interface design. To a user, there’s no difference between installing a local or remote file, there’s no real difference between that and removing package, and searching through packages should be there too, because all 4 things have the word “package” in them. A developer can see the difference; a user can’t, and shouldn’t have to. Not only do they want one tool that does all this, it shouldn’t be a file manager, because from a task-based point of view, copying/deleting/opening files has nothing to do with packages.

    [ Reply | Parent ]

    Based on: PHP-Nuke

    All logos and trademarks in this site are property of their respective owner. The comments are property of their posters, all the rest © 2000 by Debian Planet

    You can syndicate our news using the file backend.php.