Debian Planet

Welcome to Debian Planet


All your woody are (not quite, but very very very soon) belong to us.
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, 108 guest(s) and 9 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: Debian from source (Score: 1)
    by AnswerGuy on Friday, May 24 @ 22:59:41 BST
    (User Info)

    This is a solution looking for a problem. Either that or it’s woefully incomplete. All this does is fetch the sources for each of your installed packages and builds them. It doesn’t recurse (easy enough to add) and it doesn’t handle failures. (Any mirror that’s down can break the script).

    Mostly it doesn’t actually give you anything different than the auto-built binary .deps. We’d have to write a gnarly little gcc wrapper to add/replace machine/processor optimatization switches (for what you seem to be asking about) and we’d probably find that many of the resultant packages failed to build or had subtle bugs as a result of inappropriate CPU optimizations.

    To make an “Optimized” Debian maintainable we’d want to work with the maintainers and have a switch or hook that allowed the build host to run a “configure” script and generate a base set of compiler flags. This is a gross oversimplification since Debian has C, C++, Objective-C, and many other sorts of source code; and most of this discussion only relates to C/C++

    A question then becomes: what other “aspects” could be separated from the packages and managed by the builder? (I’m referring, vaguely, to AOP, aspect oriented programming, here). Back to my initial comment: What is/are the problem(s) to

    which this is (part of) a solution?

    BTW: my script also fails if it encounters a

    build-dep that points to a virtual package; like

    the kernel-headers-2.4 (virt)package which is supplied by one of the more specific kernel-headers-2.4.18-xxx-smp or similar real packages.

    [ No Comments Allowed for Anonymous, please register | 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.