Re: [Flightgear-devel] nasal can't follow symlinks anmore?

[Rebecca N. P. <reb...@zo...>]

> I store them in "/media/fg/fgfs/Custom/Aircraft/available/"
> If i cloned TheOmegaHangar A330-300 the folder is called
> "/home/dirk/.fgfs/Custom/Aircraft/avialable/airbus-a330-300-main/"
Is it /home/dirk/.fgfs/...  or /media/fg/fgfs/... ?  If the first, we 
have another bug here: symlinks are only supposed to be rejected when 
they point to a non-allowed directory, and all of FG_HOME (by default 
.fgfs) is allowed for reading.

> https://gitorious.org/fg-airbus-a333/airbus-a330-300-main.git
> seams closed :-(
Gitorious closed down (and was replaced by Gitlab, but projects were 
only moved over if they asked to be, which this one does not appear to 
have), so I can't test this particular aircraft, but it does appear to 
be common (necessary?) for aircraft to contain "Aircraft/<expected 
folder name>/..." paths, which break if they are moved (with messages 
like "Cannot find Nasal script 'Aircraft/A340-600/Nasal/systems.nas' for 
module 'b777'.").

This should be fixable by renaming the aircraft's folder to what it 
expects: while git initially sets the top-level folder name to the 
repository name, it doesn't use that name to find the repository.