Hi All, 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. (I think this was suggested a few weeks back, but I'm formalizing the rfc.) Thoughts? Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.
