dev builds
themes manual
device status forums
mailing lists
IRC bugs
dev guide

Rockbox mail archive

Subject: Re: [RaaA] Weekly status report

Re: [RaaA] Weekly status report

From: Daniel Stenberg <>
Date: Mon, 14 Jun 2010 16:31:09 +0200 (CEST)

On Mon, 14 Jun 2010, Thomas Martitz wrote:

> a) We collected some ideas two weeks ago but we didn't manage to find a
> consensus I think. I still think exposing the full / is unnecessary but OTOH
> I wouldn't want to limit users.

I think / by default and a command line argument to set another one by choice.

> b) Where to install it? /usr/local/bin (or C:\Program Files\Rockbox) comes
> into my mind

I assume your program will use configure to build on *nix? Then /usr/local/bin
should and will indeed be the default. I assume ./configure --prefix will be
supported if you want to fiddle.

People who build packages for distros will of course pick what's suitable for

> then there's the problem of not having write access in the installation
> routine.

Not really. /usr/local/bin is the generic default for 'make install' since the
dawn of time. There is no reason to change this imho.

> Installing somewhere into $HOME seems weird.

That's what ./configure --prefix is for. Or make DESTDIR.

> Another idea would be installing the binaries to /usr/local/bin, the
> plugins/codecs to /usr/local/share, and see what changes are needed to
> de-attach them from the .rockbox directory.

No, the plugins should not be in /usr/local/share as they cannot be shared
between different systems. I think they should be in /usr/local/lib or perhaps
in a dedicated subdirectory or something.

Received on 2010-06-14

Page template was last modified "Tue Sep 7 00:00:02 2021" The Rockbox Crew -- Privacy Policy