Slashdot Mirror


X.Org Releases First Modular Source Roll-Up

NewsForge is reporting that X.Org has released their first modular roll-up release. From the article: "All X11R7.0 derivative ("modularized") releases divide the source code into logically distinct modules, separately developed, built, and maintained by the community of X.Org developers. This concentrates and accelerates development time, supporting continuous modification, testing, and publication of each module.The new modular format offers focused development, and rapid and independent updates and distribution of tested modular components as they are ready, freed from the biennial maintenance release timetable."

18 of 176 comments (clear)

  1. I, For One, Welcome Our Modular Overlairds.... by branteaton · · Score: 3, Interesting

    I could not be happier. Modular design clarifies architecture and simplifies targeted enhancements. Better X, faster. What's not to like?

    --
    this .sig intentionally inane.
  2. Gentoo by binkzz · · Score: 3, Informative

    This should make it a whole lot easier on the Gentoo user machines - we will no longer have to recompile the entire X.Org source on every update.

    I heard rumours of KDE going a similar route in the future.

    --
    'For we walk by faith, not by sight.' II Corinthians 5:7
    1. Re:Gentoo by rdwald · · Score: 3, Informative

      There's a difference between hard-masking and keyword masking. Essentially, Gentoo has three levels of packages: "stable," "masked," and "hard-masked." Masking involves just putting a tilde in front of your architecture to get the software. You can use the /etc/portage/package.keywords file to specify packages you always want the masked version of; I've done this with Firefox, for example. There's another level of masking, which is called hard-masking. To remove a hard-mask, you've got to put the package in /etc/portage/package.unmask, and you need to list a specific version of the software you want to unmask. In general, it seems reasonable to have a few masked things installed on your system, but these aren't the same as hard-masked packages.

    2. Re:Gentoo by Frogbert · · Score: 5, Funny

      That would be really cool. In the meantime though I would like to suggest a system where most common large "packages" of software were compiled and posted some place on the net that Gentoo users could download them. That way everytime there was a point release they wouldn't have to spend ages recompiling. Sure there may be a slight hit to performance but given the inherrent redundancy of compiling the same packages thousands of times on every users computers to just a few times for major architecture it makes sense to me. /runs for cover.

    3. Re:Gentoo by Frogbert · · Score: 5, Funny

             (J) <--- The joke
             ...
             ( )
            __|__     <--- You
              |
             / \

  3. Good thing! by gweihir · · Score: 4, Informative

    A monolithic system with poor or unstable interfaces is a maintenance nightmare. Maybe this explains why in the end XFree86 was so slow in supporting new hardware drivers. I still remember having had to patch the sources manually for my ATI Radeon 9600XT card, just because the PCI ID of that card was still not in the release quite some time after the card was on the market. Really bad.

    With a modular built, they can now change one part, like the drivers, with little fear of introducing problems in other parts. High time this happened. I am looking forward to the things to come.

    --
    Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    1. Re:Good thing! by r_jensen11 · · Score: 5, Interesting
      The major drivers that most users have issues with are with the proprietary video drivers, though. We can only hope that this will help us get driver updates as fast as Windows users, but we have no idea if ATI and nVidia are actually going to help the end-users any more than they currently do.

      I think the main thing that this will allow us to do is have more features added/modified, rather than more/newer drivers.

  4. Re:Still doesn't fix by siride · · Score: 3, Informative

    You don't understand what modular means in this case. It only means that the various components of X are now in separate autotooled packages. There hasn't been any change in the existing modules, only now they are available separately rather than as part of a single monolithic tarball with a monolithic build system.

  5. The kernel should go the same way! by bunbuntheminilop · · Score: 3, Funny

    Its like a fasionable thing to do nowdays.

  6. X11R7.0 was already modular. by Morty · · Score: 5, Informative

    X.org has been modular for a while -- X11R7.0 was already modular in December 2005. The real news here is that X.org released X11R7.1, not that they've gone modular.

    One thing I'd like to see is an ordered list of dependencies. I still do manual builds on one system, to stay in practice. Building X11R7.0 was so painful, I stuck with X11R6.9. When using a distro that does the heavy lifting, X11R7.0 is great, but sorting out the dependencies in dozens of modules is a PITA if you're trying to build it manually. I bet the distro maintainers are cursing the X.org people.

  7. But..!? by hey · · Score: 5, Funny

    So they broke it up into pieces and a we are now celebrating the
    release of the pieces rollde together into a monolithic whole!?

  8. Accelerated Indirect GLX! Woowoo. by Anonymous Coward · · Score: 5, Interesting

    Accelerated indirect GLX has been a until recently been a unattainable holy grain for a long time now in regards to X.

    What this will allow you to do would be allow users to gain some benifits from having hardware acceleration for 3d and multimedia application even when running applications remotely over a network.

    Another way to put it is that applications gain their acceleration not from the hardware directly, but from the Xserver they are running on, which then itself then uses the hardware acceleration.

    It's not going to be as fast or efficient as direct rendering, but it's much more flexible and usefull in a wider context.

    It is another stepping stone to having a fully realised opengl-based X server.

    This is probably very much due to Redhat's AIGLX specificly and xgl development in general.

    1. Re:Accelerated Indirect GLX! Woowoo. by RedNovember · · Score: 5, Funny
      Accelerated indirect GLX has been a until recently been a unattainable holy grain

      I'll say. I've been waiting for accelerated indirect GLX beer for a while now. Booze Informer says it could unseat Old Janx Spirit as the choice smasher for Pan Galactic Gargle Blasters.

      Woo woo, indeed.

      --
      "MY APOCALYPTIC TENOR HAS NOT BEEN DISPELLED!" - T-Rex, qwantz.com
  9. Re:fruit roll-up by krmt · · Score: 4, Funny

    Go play the game Katamari Damacy. Then imagine that each random thing you add to your proto-star is one little piece of the Xorg whole. You can imagine that the server is a cow if you like.

    --

    "I may not have morals, but I have standards."

  10. Re:Still doesn't fix by AKAImBatman · · Score: 4, Insightful

    Not having to download the entire source tarball to fix one package lowers the cost of entry for people interested in making changes.

    Or more likely, being able to build a distribution without twm, xedit, xeyes, xman, xvfb, and the billions of other useless utilities that clog up and XWin installation could make for smaller, more focused builds that assist projects that are focused only on producing an end product. (Damn Small Linux is a good candidate in my mind.)

    Previously, the X build system was so monolithic in nature that you couldn't not build all these stupid little widgets. Now that things are more modularized, you can build only what you need and throw away the rest.

  11. No Need To Scrap X by krmt · · Score: 3, Informative
    The raster graphics are horrible. I realize that redesigning the rendering system will be arduous and time consuming. But I think it wold be nice if the *nix rendering system would advance past the 70's.
    Done.
    --

    "I may not have morals, but I have standards."

  12. Re:Why not scrap X by Eric+Smith · · Score: 4, Interesting
    I realize that redesigning the rendering system will be arduous and time consuming. But I think it wold be nice if the *nix rendering system would advance past the 70's.
    How about explaining exactly what is wrong with the X rendering system, rather than just complaining about it? Are you talking about Xlib? There are certainly better APIs already available, such as Cairo.

    X seems to work OK for me, and doesn't seem substantially less functional than the Windows or Mac OS models.

  13. Re:In other news ... by msh104 · · Score: 3, Informative

    it never died. it's just developing even slower then before. but they did already made another release after the split before this one, which didn't got any coverage on slashdot either. it looks like the open source comminity has choosen to silence it to death. :p