I've just switched to redmine as installed in portage. Since this is a server, I find it a bad thing that redmine is installed to /var/lib/redmine without a version string. In case a upgrade fails, it's very important to keep an old working copy around. Upgrades have to be done manually anyway, so I'd favor a solution where redmine gets installed into /var/lib/redmine-0.9.4 (or whatever your version is) and have the user upgrade whenever he sees fir Reproducible: Always
Hello Benjamin, the files in the / tree get replaced only after the emerge completed w/o errors. You can preserve the old version of the package by using `quickpg <atom>`, this stores a tarball to /usr/portage/packages and can be reinstalled later with `emerge -av -K <atom>` (watch `eix` output, there is a "{tbz2}" after these packages). Can you live with that options? Michael
Well, I'm not sure... the thing I have problems with the most. Say the update to 1.0 happens. The database layout will change. If anybody accesses redmine before the upgrade procudure has been complete, the outcome might be disastrous - corrupted db, whatever. And this will happen - when you get 200 updates it's likely you miss the redmine one. That's why I think installing into separate directories makes more sense. Move files, run migration script and once that's done, switch the entry in the vhost and that's it. I think that's a lot more safe!
So you suggest slotting every version of redmine?
What I'd like to prevent is the following: - The user has a redmine server running - he runs a world update which updates redmine - redmine breaks until its fixed by running emerge --config I don't know whether this is easily possible. I started using /var/lib/redmine and I do see the convenience in using this Cheers Benjamin
Benjamin, as far as I understand what you want can be solved with specific portage configuration (see bashrc section): http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=3&chap=6#doc_chap3 So just configure your system and it'll run emerge --config every time package is upgraded. Note in general not everybody want this. For example, on build server (where I create packages) I don't want any database initialization/upgrade steps happen. Until I miss anything, closing this bug as INVALID (not a bug). Fell free to reopen if you disagree.
