On 13/07/10, 02:12:45, Ben Walton <[email protected]> wrote regarding [csw-maintainers] [RFC] splitting cswclassutils:
> I'd like to propose that cswclassutils be split as follows: > 1. Each i/r script pair becomes a separate package named CSWcu-foo > 2. CSWclassutils becomes an empty package depending on all CSWcu-foo > packages. It will only change when we add/remove a CSWcu-foo > package. > This would make bug tracking nicer as it currently burdens Peter B > even when he's not the author/maintainer of the script in question. > It should also make coordination of the package easier as one person > isn't repsonsible for ensuring that all separate script updates have > been tested before asking for a new release, etc. CSWcswclassutils has to be manually installed in the global zone, splitting it will make package management harder. Having a single responsible person should be a good thing, like having a prime contractor. The best way to reduce the maintainer burden is to stop fiddling with it. James. _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.
