We need to start with this as we only have our developer for 1 month. He has already written some code for this project.
I see 3 main areas, some of these we have more done than others.
1. a) Determine if there is a new errata b) Download description of errata c) Download .src.rpm
2. Build rpm out of .src.rpm
3. a) Populate ftp/http areas with new errata b) Send mail to mailing list containing description and rpms updated.
I think we both already have item 2. We currently do item 1 manually. The populate part of item 3 we have automated along with the list of rpms updated. We manually do the descriptions.
So our work will focus on item 1 parts a,b,c and item 3 part b.
Have you done any of this work yet?
Is there someother place where we should be having these discusions.
-Connie Sieh On Mon, 19 Dec 2005, Connie Sieh wrote:
On Mon, 19 Dec 2005, Jim Perrin wrote:
On 12/19/05, Karanbir Singh mail-lists@karan.org wrote:
Connie Sieh wrote:
Centos-devel,
Do you have scripts/code to harvest RedHat SRPMS for errata? Rebuild the .src.rpms and then send out email with the "technical" details included?
Trying to automate our release system more than it is now.
Thanks
-Connie Sieh
Scientific Linux Developer
Hi Connie,
We are actually working on something of this nature ourselves.
--
Would it be considered heresy to suggest combining forces on this one?
Not as far as we are concerned. I think Troy talked to some of the CentOS developers at the February Linux World in Boston about working together on some projects.
-- Jim Perrin System Architect - UIT Ft Gordon & US Army Signal Center _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
-Connie Sieh _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel