I am evaulating paludis as a package management system for the Chromium OS project. There is currently some functionality missing that Chromium OS needs, and I was hoping to get some feedback on the paludis community interest in these features. Specifically, is there a good chance that patches providing these features would be accepted?
The following is the list of features I'll be working on (in order of priority): * support package.keywords / package.unmask in profiles These 2 files are documented in portage man-pages, but currently no repositories is using it except for chromium-overlay. I just submitted ticket #954 for package.keywords, and I think package.unmask is no harder. * binary packages (PBIN?) Seems like paludis is actively working on this, but I'm not so sure about the current progress. Is there any work that I can help with? * parallel compile/install/merge Similar to portage-2.2's --jobs option. * separate host/target dependencies As proposed in Gentoo Bugs #201499, to distinguish host/target build-time dependencies using label-based dependency. Paludis should be able to load two sets of configuration files for host/target respectively, determine correct dependency & build order, and build packages using the correct environment. * smart rebuild for -scm packages Add a hook in src_fetch or src_unpack stage, so the ebuild can report if the source revision has been changed since last build. Also, the scm revision should be included in package metadata, so the version of pbin files can be checked against the source code. (and rebuild should be done if mismatch) Best regards, Tien-Ren Chen, 2010/08/09. _______________________________________________ paludis-user mailing list [email protected] http://lists.pioto.org/mailman/listinfo/paludis-user
