>> Have we considered bundling any packages with the MacPorts disk images that >> most packages use? > > No, I don't think we've considered that. What would be the benefit? Ports > aren't hard to compile the usual way...
Example: if zlib is required by 90% of the ports we have, we should go ahead and bundle it with the installer. >> Does anyone run any statistics on what are the most depended packages? > > The port command doesn't collect statistics, and since we don't get distfiles > from a central location, we don't have download statistics for those. We > could add up the download statistics from each distfiles mirror (if we had > logs available) to get part of the picture. But if the goal of getting that > picture is to bundle pre-built packages with base, then I don't think we > should be doing that. I'd rather we look into providing binaries of any > package. You don't need download statistics: just look at the portfile dependencies and see what ends up being required the most. I'm thinking zlib is likely to be one.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
