If you like sticking explosive crossbow bolts and/or semtex sticky grenades to people and watching or listening to them explode, you should try mastering the Nuketown map. Don your flak jacket and hatchet and go at them, kamikaze style!
The biggest reasons seem to be stability and performance utilizing some features of OpenGL. It’s about time someone takes the big leap and wrangles the X monster. If you were to start from scratch right now, designing GNOME, KDE, XFCE, etc., all without Xorg’s quirks and limitations, would it come out the same? I don’t think so.
Custom RPM repositories may modify comps.xml to include custom rpms, rebuilt packages, or ports. Existing Existing groups can be modified or you can create new groups entirely. Packages can install by default, optional, mandatory, or conditional.
his little utility comes with rpm, so it’s already installed and waiting for you. rpm2cpio converts a rpm file specified as as a command argument (or as standard input) and spits it out as a cpio archive to standard output.
Utilizing macros can make life easier when you’re dealing with building on, and for, multiple platforms. Why bother with hard-coding full paths to system utilities when you can simply refer to them by their macro name? These can also be useful for avoiding things like rpm check-files errors, installed (but unpackaged) file(s) found, and debuginfo related stuff.
If you’ve ever run into a dreaded configure problem such as C compiler cannot create executables, and gotten lost in a tangle of glibc/cc/g++ packages, you might find that building source rpms using Mock turns a multi-step process into a breezy single step. Build source rpms using mock which builds inside a chroot. This lets you compile 32-bit on 64-bit without a problem. Check out mock configurations in etc. You may have preconfigured configurations for your Linux distribution.