»Click here to calculate your site FeedRank Today«
FeedRank, a newly developed algorithm for ranking RSS feeds only on RSSMicro
Click here to learn more
 6/10 Very Good --- planet.gentoo.org http://planet.gentoo.org/rss20.xml
| Planet Gentoo - http://planet.gentoo.org/ ... |
Tuesday, July 22, 2008 --- 38 days ago http://www.reactivated.net/weblog/archives/2008/07/fedora-rpm-packaging/
| Since starting at One Laptop per Child I have been doing some distro work on the OS platform for the XO laptop. The platform is based on Fedora 7 and I have been working on rebasing us onto Fedora 9 for the next release. Having very little distribution experience outside of developing Gentoo for the last few years, I’ve found some aspects of Fedora’s binary package (RPM) workflow particularly interesting: Automatically detected dependencies : In Gentoo ebuilds, we have to state that package A depends on library B. In Fedora, when building the binary package, the build tools determine many runtime dependencies automatically so there is no need for developers to manually list all dependencies in spec files. Chroot build environments : All packages are built in an otherwise-empty chroot. The build system creates a chroot, quickly installs all of the base binary packages and the build dependencies, then builds/installs a package, produces a package, and throws the chroot away. This allows for predictable build environments and is good for QA. Community access to the build box : All packages are built by Koji . Koji has a nice “scratch-build” system where you can throw a source RPM at it, and it will build it and serve it back to you on a webpage a few minutes later. Great for build testing and handy if you don’t have a complete build environment locally. The scratch-build service is open to non-developers assuming they have been through t ... |
|
|
Recent Posts
|
|
|
Facebook Del.icio.us Digg StumbleUpon Reddit Google
Anytime
