[Pkg-owncloud-maintainers] php-sabre-vobject packaging (was: Introducing myself)

[David Prévot]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi,

Le 27/03/2013 10:57, Evert Pot a écrit :

> I'm the lead dev for SabreDAV, and I just subscribed to this list.

Great, welcome, and thanks for your valuable work!

> 1. I'm going to refer to the sabredav in the future everywhere as 'sabre-dav',
> (just like sabre-vobject). For consistency, I reckon it would be good to also
> call the main package this

That could be done, sure. Even more easily that it has not yet been
shipped in Debian stable, and that we are considering removing it from
Wheezy before it becomes stable (since it will be difficult for us to
maintain the 1.6.2 version in the next few years).

> 2. Both the sabre-dav and sabre-vobject package depend on composers autoloader
> to do, well, autoloading. Is this something you guys intend to handle?

I must admit I haven’t yet put much thoughts about it, but thanks for
asking, we should have that in mind soon to make this right.

Evert, since you’re here, I’m wondering how to use the build.xml in
sabre-dav: I don’t know much about these things (I’m new at all this
ownCloud packaging), and simply running ant miserably fails for me:

	$ ant
Buildfile: /home/taffit/debian/php-sabredav/build.xml

init:

BUILD FAILED
[…]/build.xml:69: Problem: failed to create task or type adhoc-task
Cause: The name is undefined.
Action: Check the spelling.
Action: Check that any custom tasks/types have been declared.
Action: Check that any <presetdef>/<macrodef> declarations have taken place.

Thanks in advance for any advice or pointer to some documentation.

On a related note, Thomas (Goirand) just advised to maintain the new
php-sabre-vobject package under the PKG PHP PEAR group [0]. This makes
sense to me, so is there any downside to moving it? (I’d assume not and
will do so tomorrow unless someones speak against this proposal).

	0: http://bugs.debian.org/704008#14

For consistency, I guess it would also make sense to move the
php-sabredav packaging under the PKG PHP PEAR group too, and will do so
as soon as the new php-sabre-vobject package enters Sid (thus giving
more time to think about it), unless someones speak against that proposal.

Thomas (Mueller), I noticed you licensed your packaging under the
GPL-2+, may I ask you to reconsider, and use the same license as
upstream for consistency (i.e. BSD-3-clause-SabreDAV for php-sabredav,
and AGPL-3+ for owncloud)?

Regards

David

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJRU0N0AAoJELgqIXr9/gnykdsP+wcRLjSmFZcszMFL8QDQuKdn
hnQg38rk9o0tyTPBREOWs4zVZFK5pin/Ha3UTjuuFUcyrd0rr64/XqefnNZT8VS1
m6swPtXY1kBvliEOKv0StLvmqhso902CMzcXLpj9drwjVyx+U3JFfh1kQCm6HIlh
vg5js185/U3J6h10Im7tsvp2IzaA5lX3gzi/dff8tSWltDz5mXSQIk1MxNp8tzE+
+lL4BtXJK+C5FXXs486jo8PTKMHwtQTCN9bUaviF6+QM1Vr8ypVXL+5tBhVYh/w2
Dnw3PRWru3r165DMR4BaeJOHsviPDv8cOeulgGqzGgaDcFfpUBbq9VKQxfZn5Twz
xxhXLNM66JHHrvsVQubkPRFTdr/PKkFMSBcX7A3IDR7gIeoKo9PfAUb22Vza+rz+
WKVzUfD/fnt1JbpeLruNJ4dp9mTB/EYKkGR5+JI1orkTDUfpmUEeyE+fJmEBZY4G
KkjR+GjiS33qsasYSyJofkSuiaAXcMQO19zEe+yuGjkgy1zwKEKfSGoLn1/BTJPS
tMiFE67dASLn7BHXueeNEWf21rylJU67681Ssz0gdlvO3lCSuwNH/z/eFq6sSZ/1
hVkIrKuhm+LVrnkpt8RzSSeBS/E58MvkyoqlyQq1PXTBaxguNuv8NpY7P9eyPCU4
lGu1fx+HpXjNMjY1znCN
=diH0
-----END PGP SIGNATURE-----