Wel that happens when you want to have the database names changed, because you do find the names "LATEST" vague and want it changed on the spot.
Then It is not easy to make a change when the same configuration change needs to be made at several places. having a configuration at one and the same place would prevent this
So I made the change, because Pierre didn't like the "LATEST" tag in the name.
I made the changes in the yaml file that I knew would break, if there was an other place ... that needed fixing well then that one broke.
Who to blame... The one who wanted the change, the one that made the change and/or the one that made it such that it can brake ... make your choice.
cheers
Stephane
On 28 Nov 2011, at 18:07, Thomas Abeel wrote:
On 11/28/2011 11:32 AM, Lieven Sterck wrote:
apparently the problem only exists from spidermite ....
after looking into it, it turns out that the genomic DB is not found
anymore because it has changed names ???
Thanks for fixing it!
Any idea who changed the genomic DB name? So we can attribute proper blame! These things should not happen, I guess we can all agree on that. So let's find out what went wrong, who made the mistake and make sure it never happens again. Either by putting technical limitations in place or by having Pierre have a little chat with the perpetrator ;-).
cheers,
Thomas
===================================================
Stephane Rombauts Principal Scientific staff
Bioinformatics & Systems Biology
Division of the Plant Systems Biology Department
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~