Re: [Flightgear-devel] Addon livery handling

[James T. <ja...@fl...>]

> On 8 Jun 2023, at 15:21, merspieler <mer...@al...> wrote:
> 
> On Thu Jun 8, 2023 at 11:51 AM CEST, James Turner wrote:
>> I’ve had a bit more of a thought about this, and slightly changed my
>> mind, but, I think it’s mostly okay for you. Basically you should use
>> resolvepath(), and assume some prefix (‘Liveries’ is probably a good
>> idea) in the paths you look for.
> 
> As we said, the overlay thingy does that for us.

Okay :)

> 
>> This is the same as we already discussed. (Ignoring problems with Nasal
>> permissions / symlinks which I’m still waiting to hear back about)
> 
> This one line change we've written (adding Liveries/<aircraft-id>)
> triggers the issue for us.

That makes very little sense to me, and you’re going to need to debug it yourself in detail, eg using GDB / strace or something to see what paths it’s looking at (or maybe set the log level to BULK ?)

> 
> Am I right, that this doesn't really change anything for us ad just the
> user needs to place stuff $somewhere-else?
> If so, where?

They place it wherever they want, but add that path via —data (on the command line). What the user can’t to do today (but we will fix it) is specify the $somewhere-else location via the Launcher UI. Of course we can fix that before the next stable release.

Kind regards,
James