Looking at still progressing survey(currently more than 50 responses), I still see, that nobody uses server:database:UNSTABLE repository in openSUSE Build Service. So I have an idea to drop it completely – whole repository – and move packages that are only there (like MariaDB 5.3 or MySQL Community Server 5.6) to the server:database repository. This might make it easier for people to find these packages. But it has some downsides as well. Original purpose of UNSTABLE repository was to have it in name that this contains alpha/beta versions and that it may not work or worse. Once I will move it to the server:database repository, only distinction would be summary and package name. And who read the summary… I guess I will go for it and we will see. But if you have some strong arguments against, speak now, otherwise I will proceed in next few days
Oct 12
server:database:UNSTABLE and server:database merge
Permanent link to this article: http://michal.hrusecky.net/2011/10/serverdatabaseunstable-and-serverdatabase-merge/



5 comments
Skip to comment form ↓
Manuel Trujillo
October 12, 2011 at 17:54 (UTC 2) Link to this comment
I think that if you remove the UNSTABLE repo you will be making a wrong thing, because like you are saying, the DATABASE repo is for “production ready products”, and UNSTABLE is for Alpha/Beta products. I do not think it’s a good idea.
Have a nice day
TooManySecrets
Michal Hrušecký
October 12, 2011 at 19:13 (UTC 2) Link to this comment
Well, server:database is also kind of bleeding edge (it’s stuff that will go to the Factory) and 20% of people in the survey wanted bleeding edge stuff although they don’t use UNSTABLE repo. Of course it wouldn’t be enabled automatically, you will have to switch to it manually, but it will be more visible and hopefully more used…
Manuel Trujillo
October 12, 2011 at 19:38 (UTC 2) Link to this comment
Well, run a MySQL 5.5.x isn’t “bleeding edge” (I think). BTW, run a MySQL 5.6.x yes.
IMHO I think the server:database would be a database repo for production, with databases “reading for production”. I think that means nothing to the openSUSE distribution maintains a particular version of, for example, MySQL 5.1, when the latest stable and ready for production is 5.5.
Please, sorry for my bad english, is a big slowdown when I try to express me in things like that.
At least that is my opinion, but the work and the repos are yours
Thanks to be opened to others ideas.
Have a nice day
TooManySecrets
Michal Hrušecký
October 12, 2011 at 21:07 (UTC 2) Link to this comment
Well, difference is that if you add
server:databaserepository after installing openSUSE, you will get almost automatically (repository change) updates to the stable MySQL (currently 5.5.x and if you are running 5.1.x, you would get 5.5.x anyway), but to switch to the betas (5.6.x) you would have to explicitly install MySQL 5.6. I guess I could do something similar for 5.1.x if somebody wants to stick to it…. I understand that it may bring some confusion but currently it looks like that people can’t find unstable repository. And I hope that if I would kill:UNSTABLErepository it will also lower the expectations. My guess is that anybody who would explicitly switch to 5.6 series either knows what he is doing (so no harm can be done) or is completely clueless (dangerous to have root privileges anyway).But many thanks for your feedback. It’s always great to hear that somebody cares!
Manuel Trujillo
October 12, 2011 at 21:41 (UTC 2) Link to this comment
Nopes. As I said before, the thanks are for you and your great work and dedication
Have a nice day
TooManySecrets