manphiz <manphiz%gmail.com@localhost> writes: > Thanks for the explanation Greg. Your new addition to cyrus-sasl's > DESCR is the next best thing to have, though I'd still like to see > that metapackage to be implemented :) I'll try to contribute a patch > once I become more familiar with pkgsrc. A metapackage might ok, but I think it will be difficult to include the ones everyone wants and not include the ones that people think are bloat. However, we have some metapackages that are explicity for testing, as in "build everything that depends on foo, for some known-troublesome package foo". Plus, I suspect some plugins have their own dependencies, so the footprint of a metapackage that includes all fo them might be large. But if you want to play with that in your own checkout and understand the consequences as a way to learn pkgsrc, you should feel free. A metapackage is pretty easy as there are examples to steal from. It's basically just a list of other packages, but it's more complicated than that. You are welcome to as for access to pkgsrc-wip and create a metapackage there. http://pkgsrc.org/wip/
Attachment:
signature.asc
Description: PGP signature