finddir returns non-existing B_USER_ADDONS_DIRECTORY

[ahwayakchih]

/> finddir B_USER_ADDONS_DIRECTORY
/boot/home/config/add-ons

/boot/home/config/add-ons does not exist. The only existing user's add-ons that actually works (Tracker finds add-ons there) is /boot/home/config/non-packaged/add-ons/.

I'm guessing that the old, BeOS path should be supported for compatibility (at least in R1), so maybe the easiest way would be to create symlink from /boot/home/config/add-ons to /boot/home/config/non-packaged/add-ons?

Or maybe both should be existing and supported by Tracker (and other tools and apps)?

[waddlesplash]

That directory would be read only even if it did exist; the non packaged one is the one to use if you want to write into it. But you probably want to use FindPaths, which will find all relevant paths.

BeOS applications will get the non packaged path automatically I believe.

[waddlesplash]

I guess we should probably write a document explaining how this all works for developers, though.

[ahwayakchih]

Thanks for the answer :).

What do you mean by:

BeOS applications will get the non packaged path automatically I believe.

Do you mean that C++ API returns valid path, and it's just the finddir application that returns original BeOS path when called from command line (or script)?

I guess we should probably write a document explaining how this all works for developers, though.

Yeah, that would be great :).

I was using finddir in my makefile before. I guess now it's not that important, because we have repos with packages (building package is next on my new-things-to-learn list :), but still... getting non-exitant path from command line "API" is a bit confusing.