server and sail-server should conflict on Centos.

[evil_steve]

Under Centos, Packages OurDelta-server and OurDelta-Sail-server are pulled down together, but should conflict with each other.

If it's as bleeding edge as discussion on IRC has indicated, Sail-server should probably live in a "testing" repo of some sort, but I think it's important to make sure that all OurDelta packages Conflicts: and Obsoletes: the other Mysql packages and separate them repo-wise.

[sjw@localhost rpmbuild]$ sudo yum update
Loading "fastestmirror" plugin
Loading mirror speeds from cached hostfile
 * OurDelta: ourdelta.org
 * base: gateway:8080
 * updates: gateway:8080
 * addons: gateway:8080
 * extras: gateway:8080
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package MySQL-OurDelta-server.i386 0:5.0.67.d6-0.el5_2 set to be updated
---> Package MySQL-OurDelta-Sail-server.i386 0:5.0.67.d6-0.el5_2 set to be updated
--> Processing Dependency: libmysqlclient.so.15 for package: php-mysql
--> Processing Dependency: libmysqlclient.so.15 for package: perl-DBD-MySQL
--> Processing Dependency: libmysqlclient.so.15(libmysqlclient_15) for package: php-mysql
--> Processing Dependency: libmysqlclient.so.15(libmysqlclient_15) for package: perl-DBD-MySQL
--> Running transaction check
---> Package MySQL-OurDelta-shared.i386 0:5.0.67.d6-0.el5_2 set to be updated
--> Finished Dependency Resolution

Dependencies Resolved

=============================================================================
 Package Arch Version Repository Size
=============================================================================
Installing:
 MySQL-OurDelta-Sail-server i386 5.0.67.d6-0.el5_2 ourdelta 17 M
     replacing mysql.i386 5.0.45-7.el5

 MySQL-OurDelta-server i386 5.0.67.d6-0.el5_2 ourdelta 17 M
     replacing mysql.i386 5.0.45-7.el5

Installing for dependencies:
 MySQL-OurDelta-shared i386 5.0.67.d6-0.el5_2 ourdelta 1.7 M

Transaction Summary
=============================================================================
Install 3 Package(s)
Update 0 Package(s)
Remove 0 Package(s)

Total download size: 37 M
Is this ok [y/N]: N
Exiting on user Command

[Mikael Fridh (frimik)]

Separating in repositories does have advantages I think.

1. The distribution of choice is selected by adding and prioritizing the repositories correctly, not by knowing exactly what the package names are.
2. After adding a repo, everything else will still "just work"; yum install mysql-server, yum groupinstall "MySQL Database".

You could for example add the repo already in the kickstart phase, simply by doing that and having the packages Provides/Obsoletes: mysql-server, you will get either CentOS-Base / OurDelta-Base / OurDelta-Testing.

Alot of this is a matter of taste I guess. I suggest discussing and testing before making too many changes to the structure at the moment.

[evil_steve (steve-nerdvana)]

Resolution:
Change folder structure to be ourdelta/$releasever/$basearch (considered "base") and ourdelta-sail/$releasever/$basearch (considered "testing") with matching stanzas in ourdelta.repo;

[OurDelta]
#base repo
name=el-$releasever - OurDelta packages for $basearch
baseurl=http://mirror.ourdelta.org/yum/CentOS/ourdelta/$releasever/$basearch
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-OurDelta
enabled=1
gpgcheck=1
protect=1

[OurDelta-Sail]
#Testing repo
name=el-$releasever - OurDelta Testing packages for $basearch
baseurl=http://mirror.ourdelta.org/yum/CentOS/ourdelta-sail/$releasever/$basearch
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-OurDelta
enabled=0
gpgcheck=1
protect=1