Bug 355509 – Dropbox ebuild

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description wyvern5 2011-02-19 02:22:24 UTC]

There's another Dropbox package that *isn't* just the nautilus extension. It's rather hidden, though.

The link on http://wiki.dropbox.com/TipsAndTricks/TextBasedLinuxInstall for x86_64 (I have a 64 bit box, so that's the only one I tried) points to http://www.dropbox.com/download/?plat=lnx.x86_64 which downloads a completely different package than what you get when you follow the obvious links to download the client (you'll get https://www.dropbox.com/downloading?os=lnx).

When you download the resulting tarball, it will decompress into a '.dropbox-dist' directory. Note the leading period.

Inside that directory is 'dropbox' executable that works just fine. It runs in the system tray just like the client for other OSs.

Reproducible: Always

[Comment 1 Chris Bandy 2011-02-25 00:12:45 UTC]

Me too. Though the wiki article is about text-based installs, the binary runs in the system tray and behaves quite well in KDE. During the first run, it presents a GUI wizard prompting for account details, destination folders, etc.

There are some ebuilds in the wild already[1] as well as contributed init.d scripts in the Dropbox wiki[2].

[1] http://gpo.zugaina.org/net-misc/dropbox
[2] http://wiki.dropbox.com/TipsAndTricks/TextBasedLinuxInstall/GentooStartup

[Comment 2 Peter Volkov (RETIRED) 2011-07-28 08:55:25 UTC]

ebuild was added to the tree by Naohiro.

Naohiro, please, search bugzilla before commiting ebuilds to the tree :)

[Comment 3 Peter Volkov (RETIRED) 2011-07-28 09:20:31 UTC]

Also current ebuild emits:

 * QA Notice: Files built without respecting LDFLAGS have been detected
 *  Please include the following list of files in your report:
 * /opt/dropbox/_heapq.so
...

I've commited fix for this issue:

@@ -15,6 +15,7 @@
 IUSE=""
 RESTRICT="mirror strip"
 
+QA_DT_HASH="opt/${PN}/.*"
 QA_EXECSTACK_x86="opt/dropbox/_ctypes.so"
 QA_EXECSTACK_amd64="opt/dropbox/_ctypes.so"
 
Also I've ported EAPI to EAPI=4 as it's always best to use most recent EAPI. If there are any problems with this, please, tell me and I'll fix. In any case this bug is fixed and if there are any further problem, please, report them separately.