>>>>> "SJS" == Stephen John Smoogen <smo...@gmail.com> writes:
SJS> My question is how slow is slow. They are looking to do monthly or SJS> faster updates of OwnCloud with non-skippable schema changes each SJS> update. Uh.... Do they at least store a schema version or something so that the updates can be automated. I know proper software engineering can be difficult, but wow. I shudder to think about how someone would deal with that in an environment where they want any kind of stability. We have the Horde suite currently which isn't "designed" to be packaged and which has occasional database schema updates, but they aren't applied automatically by the packaging process. It just warns the admin upon login that some schemas are out of date. It can update itself through a number of schema changes without the need to run external tools (though they do provide one). It's no big deal because they seem to have used more than three brain cells to design the thing. SJS> If the maintainer wants to do this then I am not going to stop SJS> them, but the upstream is really pushing the "we will find every SJS> way to make sure distributions don't use us" methods. This boggles the mind. However, there is a compromise possible. We provide packages which do all of the setup that we'd do (pulling in dependencies and such) and provide a tool which just gets the software from upstream (and maybe some cron jobs to keep it updated). That way people get an experience that's mostly like having something packaged without having a pissing contest against upstream stupidity. - J< _______________________________________________ epel-devel mailing list epel-de...@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/epel-de...@lists.fedoraproject.org
