Packaging issues

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Packaging issues

Ryan Rix
Hey one and all,

Congrats on the 1.0 release, I like what I see :) As a user..

A lot of you probably know me around KDE, and my involvement upstream as a
packager in Fedora's KDE SIG, so, yeah, hi :) I've been hacking on RPM
packages for ownCloud since about rc1, and I have a few issues that, afaict,
are blocking inclusion in Fedora's main repositories. At some point in the
future, I would *love* to see ownCloud deployed for Fedora users or
contributors when it is more mature; it's something I've had in mind since I
first attended Frank's keynote at Camp in january. But that requires RPM
packages.

But enough aimless ramblings :)

A few things I would hope to see fixed in 1.1, or sooner even, so that we
could have an easy to deploy Fedora packages:

Right now, the current setup for most Fedora web applications is to have them
installed into /usr/share, simply because it's impossible to predict where the
httpd is looking for web applications; it could be /var/www/html/, or it could
be some user specified location, or many locations (on a multi-user system).
After it is installed, it's implied that users will softlink it to their
webroot.

Of course, this setup doesn't really work out of the box, as the data/
directory wouldn't be writable by the apache user, nor should user data be in
the /usr/share tree. As a result, I've had the idea to set
/var/lib/owncloud/data as the datadir. I'm curious to know ownCloud's
multiuser plans, and how that would work with such a distropackage set up.

Secondly, the method fedora users use, to symlink to the webroot directory,
simply doesn't work with how ownCloud calculates $WEBROOT in inc/lib_base.php
starting on line 35. The combination of __FILE__ (which points to /usr/share)
and $_SERVER["DOCUMENTROOT"] (/var/www/html) doesn't play well together at
all. That's pretty much a blocker that I would need to fix to make this
package work in Fedora... Of course, I don't know PHP well enough to make
something work. ;(

Ryan

--
Ryan Rix
== http://hackersramblings.wordpress.com | http://rix.si/ ==
== http://rix.si/page/contact/ if you need a word         ==
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/owncloud/attachments/20100624/27c77ce4/attachment.sig 

Reply | Threaded
Open this post in threaded view
|

Packaging issues

Robin Appelman
On Friday, June 25, 2010 06:12:06 Ryan Rix wrote:

> Hey one and all,
>
> Congrats on the 1.0 release, I like what I see :) As a user..
>
> A lot of you probably know me around KDE, and my involvement upstream as a
> packager in Fedora's KDE SIG, so, yeah, hi :) I've been hacking on RPM
> packages for ownCloud since about rc1, and I have a few issues that,
> afaict, are blocking inclusion in Fedora's main repositories. At some
> point in the future, I would *love* to see ownCloud deployed for Fedora
> users or contributors when it is more mature; it's something I've had in
> mind since I first attended Frank's keynote at Camp in january. But that
> requires RPM packages.
Packages for ownCloud would be great to have

>
> But enough aimless ramblings :)
>
> A few things I would hope to see fixed in 1.1, or sooner even, so that we
> could have an easy to deploy Fedora packages:
>
> Right now, the current setup for most Fedora web applications is to have
> them installed into /usr/share, simply because it's impossible to predict
> where the httpd is looking for web applications; it could be
> /var/www/html/, or it could be some user specified location, or many
> locations (on a multi-user system). After it is installed, it's implied
> that users will softlink it to their webroot.
>
> Of course, this setup doesn't really work out of the box, as the data/
> directory wouldn't be writable by the apache user, nor should user data be
> in the /usr/share tree. As a result, I've had the idea to set
> /var/lib/owncloud/data as the datadir. I'm curious to know ownCloud's
> multiuser plans, and how that would work with such a distropackage set up.
As it is now, each user has a subdir in the data folder, which it creates if
it doesn't exist yet on runtime
>
> Secondly, the method fedora users use, to symlink to the webroot directory,
> simply doesn't work with how ownCloud calculates $WEBROOT in
> inc/lib_base.php starting on line 35. The combination of __FILE__ (which
> points to /usr/share) and $_SERVER["DOCUMENTROOT"] (/var/www/html) doesn't
> play well together at all. That's pretty much a blocker that I would need
> to fix to make this package work in Fedora... Of course, I don't know PHP
> well enough to make something work. ;(
We got a new webroot detection yesterday which should work with symlinks and
aliases.

 - Robin Appelman