What packages to fix and import first?
Aleksey Cheusov <[email protected]>
| Newsgroups | gmane.os.netbsd.devel.pkgsrc.wip.general |
|---|---|
| Message-ID | <[email protected]> |
WIP contains huge amount of software, more than 2000 packages. What packages can be imported and in which order? What packages need to be fixed before others? I think it makes sense to use "popularity contest" provided by other systems. For example, Debian Linux provides it here http://popcon.debian.org/ In particular there they provide tarballs containing source package names with their statistics/popularity, see "Statistics by source packages sorted by fields" section. I wrote small script http://mova.org/~cheusov/pub/popcon4pkgsrc-wip/popcon4pkgsrc-wip that gets http://popcon.debian.org/source/by_inst and src_summary (unpacked) http://mova.org/~cheusov/pub/popcon4pkgsrc-wip/pkg_src_summary.txt.bz2 on input and shows how popular wip packages "are" in Debian (5-columns of numbers). Run this script like this popcon4pkgsrc-wip by_inst pkg_src_summary.txt | sort -k3nr As a result you'll obtain the following http://mova.org/~cheusov/pub/popcon4pkgsrc-wip/pkgsrc_popcon.txt Of course at the top of this list are Linux-specific things like sysvinit, e2fsprogs and glibc but below are general purpose software. Remember source packages (source tarballs) were used as an identifier, not Debian package names. The same can probably be done for Ubuntu and maybe others. Of course the popularity in Linux world doesn't mean it will be needed by NetBSD users. And of course popularity may mean nothing for some of you. You may think all this is just for fun ;-) -- Have a lot of fun. Aleksey Cheusov. ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com