etc (as they are in the official Debian package), and it The configuration files were not placed in It just unpacks everything to /var/www/htdocs or something In particular, he said it was " like a tar.gz inside a Debian That he had tried both the official Debian package and the one Martin Steigerwaldīrought the post to the attention of the Debian ownCloud package Not surprisingly, some in the distribution community took umbrageĪt Poortvliet's characterization of the situation. Ways and provides few if any of the benefits they are hunting for. Of course, this breaks in beautifully surprising You'll find packagers trying to move the ownCloudĬonfiguration php file out into the /etc folder or split up ownCloudĬore in separate packages because we maintain some external componentsĪs part of our setup. Shoehorning ownCloud (and other web apps) into their rules made forĬ/C++ apps. The distribution packagers try to do weird shit, In addition, distribution packages can make upgrading problematic, he Distributions, he said, sometimes " don't grab the rightĬode (like relying on a git tag rather than final zip files) or missĬhanges in dependencies which can break installations". Release and the distribution's package update, along with several
Owncloud stuck in maintenance mode install#
Jos Poortvliet, community manager for the ownCloud project,Ī blog entry on January 4 recommending that users eschewĭistribution-provided ownCloud packages and install only those Gulf between the upstream developers and the distribution is moreįundamental, as a recent debate about ownCloud packages for Debian revealed. Package being available from distributions motivated Mozilla'sĮxtended Support Release (ESR) program and to various efforts atĪpplication sandboxing (such as GNOME's xdg-app). The sometimes lengthy delay between an upstream release and a new
Linux distribution mechanisms have been well-documented in recent years. The hurdles of pushing new software releases out to users via
0 kommentar(er)
