On Tue, 06 Mar 2012, Jorge O. Castro wrote:
> Why do we even need a wrapper if Dropbox is
> accepting responsibility for the user's installation?
Even the upstream package is only a wrapper. They do not provide a package
that directly contains their dropboxd daemon.
> The user has already made the choice to use Dropbox, they're not going
> to care about if the package complies with Debian policy, they assume it
> acts like it does on other platforms, that it's zero touch and
> autoupdated for them.
I'm a user too and I don't agree with this. I do care about Dropbox being
properly integrated on my system without violating Debian's policy
when that is reasonably possible.
Otherwise I would have stopped maintaining this package once upstream
started providing Debian packages.
On Tue, 06 Mar 2012, Jorge O. Castro wrote:
> Why do we even need a wrapper if Dropbox is
> accepting responsibility for the user's installation?
Even the upstream package is only a wrapper. They do not provide a package
that directly contains their dropboxd daemon.
> The user has already made the choice to use Dropbox, they're not going
> to care about if the package complies with Debian policy, they assume it
> acts like it does on other platforms, that it's zero touch and
> autoupdated for them.
I'm a user too and I don't agree with this. I do care about Dropbox being
properly integrated on my system without violating Debian's policy
when that is reasonably possible.
Otherwise I would have stopped maintaining this package once upstream
started providing Debian packages.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Pre-order a copy of the Debian Administrator's Handbook and help debian- handbook. info/liberation /
liberate it: http://