Re: Version bump policies and beta packages in stable branch

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I can offer the technical solution:

MySQL comes in three mutually incompatible branches: 4.0, 4.1 and 5.0.

Thus, the XBuild tree will have three MySQL projects: mysql-4.0,
mysql-4.1 and mysql-5.0.

'mysql' is an alias for all three projects. Thus, mysql is a virtual
project.

When a user issues 'xeta install mysql' on a system that has not had
mysql installed, it will be dealt with like any other virtual
dependency -- depending on user configuration, Xeta might prompt the
user to select one between the tree; or present the three options and
exit with an error; or select a tree-specified default; etc.

When a user issues 'xeta update mysql' on a system that has had mysql
installed, it will update to the newest in the version-branch installed.

Version constraints apply to virtual projects as well; if a package
specifies '[database server] mysql::lib ge 5.0', the version
constraint reduces the choices to only mysql-5.0.




-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFAEk+sv+6a/MPcjnERAgOZAJwI0CYR0HXFMsMUHpCeCfGhSru9CACfTrT/
UU6eHuqvfmrPYGRNFkFuetM=
=K2/j
-----END PGP SIGNATURE-----