[Angstrom-devel] [RFC] Official support for OPIE in Angstrom

[Michael Krelin]

C'mon, guys, what are you arguing over?

Is there anything wrong with opie in /opt? No.
Is there anything wrong with any software having hardcoded path? Yes.

You both are right, in a sense.

Love,
H

Paul Sokolovsky wrote:
> Hello Lorn,
> 
> Wednesday, July 25, 2007, 12:26:33 AM, you wrote:
> 
>> Paul Sokolovsky wrote:
>>> 3. Restructure OPIE installation paths to be more FHS-friendly (with
>>> assumption that for OPIE images OPIE is core component, so installing
>>> it to /opt is more a historical (mis)convention).
> 
>> It is not a misconvention, /opt is a part of the FHS, it is for optional
>> add-on application packages.
> 
>> http://www.pathname.com/fhs/2.2/fhs-3.12.html
> 
>   So you, keep wanting to ignore clause about OPIE being core
> application package? ;-)
> 
>> Keeping opie tree separate in /opt allows devices to keep opie on it's
>> own partition, or even in a cramfs file.
> 
>   On which devices exactly? Because on all Angstrom devices it's
> possible to have any package "on its own partition". Actually, it's
> not tied to a device in any way, but job of the package manager and
> matter of setting few environment variables/creating few symlinks.
> (Symlink part even automated, but the corresponding tool somehow went
> into misfavor with Angstrom maintainers, hopefully that's something to
> resolve yet).
> 
>