Comment 29 for bug 909488

Revision history for this message
Raphaël Hertzog (hertzog) wrote : Re: [Bug 909488] Re: nautilus-dropbox forbids dropbox's non-free binaries to replace themselves by properly installing dropbox system-wide

Hi,

On Mon, 20 Aug 2012, Jakob Unterwurzacher wrote:
> But isn't the description of nautilus-dropbox, "Dropbox integration for
> Nautilus", misleading? Somehow, "Downloads non-free binary blob from
> somewhere" could be mentioned.

It's in the full description:

Description: Dropbox integration for Nautilus
 Nautilus Dropbox is an extension that integrates the Dropbox web service with
 your GNOME Desktop.
 .
 Installing this package will download the proprietary dropbox binary
 from dropbox.com.

> I think the downloader functionality should be split out into dropbox-
> installer, as in http://packages.ubuntu.com/precise-updates/flashplugin-
> installer . And if dropbox releases a new version, an update for the
> package could be published that re-downloads the binary (as in
> flashplugin-installer).

I don't see any benefit here.

> At the moment I'm really not sure what to do in an LTSP install. The
> weekly cronjob update is no good because it will sooner-or-later install
> a version that does not work and I won't even notice until I get bug
> reports from users.

The binaries downloaded bundle most of the required libraries, so it's
unlikely to break unless we get some major update like a libc7.

> Letting each user download 32MB to his home (the Dropbox, Inc solution)
> also seems somewhat soboptimal, but the real problem is that window that
> pops up on first start (screenshot attaced).
>
> "In oder to use Dropbox, you must download the proprietary daemon."

You don't get that if the download during the initiall install worked.

> BTW what is the "Don't show this again" for? If the user ticks this box it's
> game over for dropbox for ever?

Good question. :-)

On Mon, 20 Aug 2012, Jakob Unterwurzacher wrote:
> Lol I just tested the nautilus-dropbox solution for a new LTSP user.
> Screenshot shows what I got. @David Euresti: So the result of the
> fruitless discussion is that you included a "unsupported location" nag
> screen ( see also
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679963 ).

Yes. During my discussions with them, they argued that they did not want
to implement a special call to "dropbox update" to invite Linux users
to upgrade because they want to keep the same behaviour across all users.

And now they prove that it's perfectly doable to implement a small special
case for Linux users...

Needless to say that this behaviour really pissed me off.

Cheers,
--
Raphaël Hertzog ◈ Debian Developer

Do you like what I do? Support my free software work on Debian and Ubuntu:
http://raphaelhertzog.com/support-my-work/