I can think of a number of permutations of this issue that could result in user confusion, or potentially worse. One would be if a user removes the ourdelta apt sources entries and can't work out how to downgrade to the mysql provided by their distribution. Another could happen if several months after removing the apt sources entry and thinking that the package was now back to the normal debian version (without having manually downgraded it) having it upgraded by a new debian version, with unexpected consequences (ie. something not handled correctly in the upgrade script of the new package because it only caters for debian/ubuntu builds).
Essentially I think its best to be explicit that the package is not the stock debian/ubuntu package so that there is no chance of confusion about which mysql server they are running. I wouldn't be expecting the ability to install both packages simultaneously, so appropriate Conflicts should be added to prevent any attempt at running both on the one installation. -- use a different package name on debian/ubuntu to avoid conflict with existing distro packages https://bugs.launchpad.net/bugs/284240 You received this bug notification because you are a member of OurDelta- developers, which is the registrant for OurDelta. Status in OurDelta - Builds for MySQL: New Bug description: It is probably not the best to use the same package name as the upstream distro's as this could cause issues if their version number were to increase above the our delta version. It would be better to use a name like mysql-server-ourdelta-5.0 and similar names for all the other packages to avoid any issues. Then use the Provides field in the control file to make it compatible with the existing dependancy name. _______________________________________________ Mailing list: https://launchpad.net/~ourdelta-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~ourdelta-developers More help : https://help.launchpad.net/ListHelp
