I worked on submitpkg some more, to give more comprehensive information. It started with Phil asking for notifying which packages were new. I implemented that, and then thought that if there are whole groups of packages updated together, they should also be grouped in the e-mail. It also tells about the kinds of upgrades: is it major version upgrade (e.g. 1.2 to 2.0) or minor version upgrade (1.2 to 1.3), or only a revision change. Here's current example output:
------------8<----------------- * WARNING: no version change + bender:/home/newpkgs/autoproject-0.20,REV=2009.11.05-SunOS5.8-all-CSW.pkg.gz * minor version upgrade - from: 1.3.9,REV=2008.11.08 - to: 1.4.1,REV=2009.11.02 + bender:/home/newpkgs/cupsdev-1.4.1,REV=2009.11.02-SunOS5.8-all-CSW.pkg.gz + bender:/home/newpkgs/cupsdoc-1.4.1,REV=2009.11.02-SunOS5.8-all-CSW.pkg.gz * new package: /dev/null -> 2.4.0,REV=2009.11.09 + bender:/home/newpkgs/py_cheetah-2.4.0,REV=2009.11.09-SunOS5.8-i386-CSW.pkg.gz + bender:/home/newpkgs/py_cheetah-2.4.0,REV=2009.11.09-SunOS5.8-sparc-CSW.pkg.gz ------------8<----------------- I also added unit tests. To test submitpkg: svn co https://opencsw.svn.sourceforge.net/svnroot/opencsw/utilities cd utilities ./submit_to_newpkgs.py -h ./submit_to_newpkgs.py -p catalogname1,catalogname2,... Maciej _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers
