Christoph Maser wrote: > Am Mittwoch, den 01.07.2009, 21:34 +0200 schrieb Dag Wieers: > >> Good question. We do have SPEC files that still date back from before we >> used an automated process. I just checked what our tool would do >> (dar-diff-perl.sh) and it would in fact remove the BuildRequires >> altogether. So it is safe to assume that our parser doesn't do this >> correctly. >> >> At LinuxTag Christoph told me we should rework our perl-management tools >> in perl because all the functionality is available from modules. And I >> agree :) >> > > I am currently evaluating the already existing solutions because i think > it is easier and more useful if we use something shared and try to model > it to our needs. My favorite right now is CPANPLUS::Dist::RPM or at > least a small tool build on top of CPANPLUS. Also interesting could be > CPAN::Packager. I will test those and write up the results. Depending on > the results I will take further actions. Anyone interested in the topic > please contact me and share your opinions. > The current target is a) have a tool wich creates new specs from CPAN. > b) triger notifications from updates at CPAN. c) have a tool to > automatically update already existing spec files (i do have a very > simple shell script wich works for ~80% of the specs)
I recently came across this: http://cpanspec.sourceforge.net/ Thought I would mention it in just in case. -- David Steinbrunner _______________________________________________ suggest mailing list suggest@lists.rpmforge.net http://lists.rpmforge.net/mailman/listinfo/suggest
