from [CentOS] CentOS 5.4? anyone?
Is that a big problem for the people who write the code and have every revision preserved for posterity (and for others to learn from) in a public revision control system?
I'm not sure that I understand. Is there indeed such a public repository of the build scriptds / RPM specs used by CentOS?
That would indeed be fascinating and useful to have a look at it. (I rebuilt libvirt from RedHat SRPM, just to test the some new virtualization feature of v5.4, and going through the process I kept wondering how the CentOS team is doing it on all the packages!)
Mathieu Baudier wrote:
I'm not sure that I understand. Is there indeed such a public repository of the build scriptds / RPM specs used by CentOS?
That would indeed be fascinating and useful to have a look at it. (I rebuilt libvirt from RedHat SRPM, just to test the some new virtualization feature of v5.4, and going through the process I kept wondering how the CentOS team is doing it on all the packages!)
http://dev.centos.org/centos/buildsys/
Have fun.
Am Donnerstag, den 15.10.2009, 22:02 +0200 schrieb Miguel Di Ciurcio Filho:
Mathieu Baudier wrote:
I'm not sure that I understand. Is there indeed such a public repository of the build scriptds / RPM specs used by CentOS?
That would indeed be fascinating and useful to have a look at it. (I rebuilt libvirt from RedHat SRPM, just to test the some new virtualization feature of v5.4, and going through the process I kept wondering how the CentOS team is doing it on all the packages!)
http://dev.centos.org/centos/buildsys/
Have fun.
What fun is there to have with empty packages?
financial.com AG
Munich head office/Hauptsitz München: Maria-Probst-Str. 19 | 80939 München | Germany Frankfurt branch office/Niederlassung Frankfurt: Messeturm | Friedrich-Ebert-Anlage 49 | 60327 Frankfurt | Germany Management board/Vorstand: Dr. Steffen Boehnert | Dr. Alexis Eisenhofer | Dr. Yann Samson | Matthias Wiederwach Supervisory board/Aufsichtsrat: Dr. Dr. Ernst zur Linden (chairman/Vorsitzender) Register court/Handelsregister: Munich – HRB 128 972 | Sales tax ID number/St.Nr.: DE205 370 553
On Thu, Oct 15, 2009 at 4:02 PM, Miguel Di Ciurcio Filho miguel@ic.unicamp.br wrote:
There really doesn't look like there's a lot of packages there.
Why haven't we tried to set up Koji? (If the answer's not enough time, or not-enough knowledge, I'm willing to help if needed)
Ian
On 16/10/09 08:06, Ian Wilson wrote:
On Thu, Oct 15, 2009 at 4:02 PM, Miguel Di Ciurcio Filho miguel@ic.unicamp.br wrote:
There really doesn't look like there's a lot of packages there.
Why haven't we tried to set up Koji? (If the answer's not enough time, or not-enough knowledge, I'm willing to help if needed)
Ian
http://mirror.switch.ch/ftp/mirror/centos/5.3/os/SRPMS/
There are SRPM's there. If that's what you mean.
I believe CentOS still uses Plague (internally)
http://mirror.switch.ch/ftp/mirror/centos/5.3/os/SRPMS/
There are SRPM's there. If that's what you mean.
I believe CentOS still uses Plague (internally)
I found this mail on the dev mailing list:
[CentOS-devel] CentOS 5 build scripts http://lists.centos.org/pipermail/centos-devel/2007-May/001765.html
Build scripts seem to be private because of login/passwords etc.
Mathieu Baudier wrote on 10/15/2009 02:23 PM:
from [CentOS] CentOS 5.4? anyone?
Is that a big problem for the people who write the code and have every revision preserved for posterity (and for others to learn from) in a public revision control system?
I'm not sure that I understand. Is there indeed such a public repository of the build scriptds / RPM specs used by CentOS?
That would indeed be fascinating and useful to have a look at it. (I rebuilt libvirt from RedHat SRPM, just to test the some new virtualization feature of v5.4, and going through the process I kept wondering how the CentOS team is doing it on all the packages!)
There is a DRAFT Wiki page in progress on this. Do not expect a finished product, but see:
http://wiki.centos.org/FAQ/General/RebuildReleaseProcess
Phil
There is a DRAFT Wiki page in progress on this. Do not expect a finished product, but see:
Excellent! Exactly what I was looking for!
Thanks a lot,
Mathieu