Adding an 'AddOns' folder in Ubuntu Karmic

Commander Smivs · Post by **Smivs** » Wed Feb 17, 2010 8:14 pm

Hi All, I don't seem to have an AddOns folder so cannot install any OXPs. As I understand it this should be at
/usr/lib/GNUstep/System/Applications/AddOns
but the only folder in
/usr/lib/GNUstep/System/Applications
is Oolite.app
I think AddOns should go in the 'Applications' folder with this but it's not there and I can't add a new folder...clicking on 'File' won't allow this.
Help, please!

Post by **Kaks** » Wed Feb 17, 2010 11:30 pm

I created the AddOns folder here:

Code: Select all

~/.Oolite/AddOns

(.Oolite is a hidden folder that should already exist inside your home directory)

Hopefully, anything you drop in that AddOns directory should be picked up by Oolite.

Website · Post by **DaddyHoggy** » Wed Feb 17, 2010 11:33 pm

Smivs wrote:
Hi All, I don't seem to have an AddOns folder so cannot install any OXPs. As I understand it this should be at
/usr/lib/GNUstep/System/Applications/AddOns
but the only folder in
/usr/lib/GNUstep/System/Applications
is Oolite.app
I think AddOns should go in the 'Applications' folder with this but it's not there and I can't add a new folder...clicking on 'File' won't allow this.
Help, please!

I think you got Oolite installed there because you gave it a password when it requested it for the install - so it's effectively installed it for root - if you don't give it a password it seems to install Oolite just foe the user who was logged on at the time.

I could be wrong it's been a while since I installed Oolite on my Linux box (I recently upgraded from Gutsy to Karmic and haven't re-installed Oolite yet).

Commander Smivs · Post by **Smivs** » Wed Feb 17, 2010 11:46 pm

Nope. really can't find it. I've set the 'view' to 'show hidden files' but my home directory doesn't seem to contain a '.oolite' folder. Now I'm totally confused!

JazHaz · Post by **JazHaz** » Thu Feb 18, 2010 1:20 am

Maybe you should just try to reinstall?

Post by **Kaks** » Thu Feb 18, 2010 11:47 am

Well, even if you haven't got a .Oolite directory (in linux using the correct uppercase & lowercase characters is important!), all it's not lost.

from the console, type

Code: Select all

cd ~
mkdir .Oolite
mkdir .Oolite/AddOns

and you should be good to go.

Post by **Getafix** » Thu Feb 18, 2010 2:08 pm

The "~/.Oolite" folder is generated as soon as you execute oolite.
The oolite-saves directory is generated as soon as a save operation is necessary.

This is at least what I have just checked in a Karmic vbox, and it is irrelevant to how you have installed oolite (super or simple user).

Perhaps we should consider adding the AddOns folder during setup.
Hmmm...

Diziet Sma · Post by **Diziet Sma** » Thu Feb 18, 2010 2:12 pm

Getafix wrote:
Perhaps we should consider adding the AddOns folder during setup.
Hmmm...

I've always wondered why it wasn't created during installation.. in fact, why not put a config folder inside, while we're at it?

Post by **Getafix** » Thu Feb 18, 2010 2:17 pm

Diziet Sma wrote:
...why not put a config folder inside...

Could you elaborate a bit on that, please? (:? again)

Diziet Sma · Post by **Diziet Sma** » Thu Feb 18, 2010 2:26 pm

Well, if, for instance, you decide to edit your keyconfig.plist, the "proper" procedure is to save it to Addons/Config. Of course, it will work if it's just saved to the Addons folder, but it's neater to keep configuration files in their own folder.. If there's already an Addons/Config folder, it will encourage players to use it.

Commander McLane · Post by **Commander McLane** » Thu Feb 18, 2010 8:24 pm

Diziet Sma wrote:
Well, if, for instance, you decide to edit your keyconfig.plist, the "proper" procedure is to save it to Addons/Config. Of course, it will work if it's just saved to the Addons folder, but it's neater to keep configuration files in their own folder.. If there's already an Addons/Config folder, it will encourage players to use it.

Actually that's how it is done in Oolite 1.65 Mac version. Oolite/AddOns and Oolite/AddOns/Config are created during install.

JensAyton · Post by **JensAyton** » Fri Feb 19, 2010 1:27 pm

Commander McLane wrote:
Actually that's how it is done in Oolite 1.65 Mac version. Oolite/AddOns and Oolite/AddOns/Config are created during install.

Did someone add an installer behind my back?

Commander McLane · Post by **Commander McLane** » Fri Feb 19, 2010 2:31 pm

Ahruman wrote:
Commander McLane wrote:
Actually that's how it is done in Oolite 1.65 Mac version. Oolite/AddOns and Oolite/AddOns/Config are created during install.
Did someone add an installer behind my back?

Of course, especially for the obsolete 1.65 version.

I also have to admit that it's been quite a while since I downloaded 1.65, so my memory might not serve me too well.

But I still have oolite1.65.dmg, and just for fun I just had a look into the image. Of course technically it's not an installer, but it contains the folder "Oolite", which by default contains the folder "AddOns", which by default contains the folder "Config", which BTW by default contains "keyconfig.plist". So the important part is that Mac users of 1.65 didn't have to worry about all that. The whole structure is already there before you even have copied it into your Applications folder.

I found that very convenient back then, and would suggest making the Linux and PC versions similarly convenient, and of course I would also suggest to keep it that way in the MNSR Mac version. The only thing I would ask for is to add yet another folder "SaveGames"—or even better—"Pilots" sitting alongside the "AddOns".

Diziet Sma · Post by **Diziet Sma** » Fri Feb 19, 2010 2:38 pm

Commander McLane wrote:
I found that very convenient back then, and would suggest making the Linux and PC versions similarly convenient, and of course I would also suggest to keep it that way in the MNSR Mac version. The only thing I would ask for is to add yet another folder "SaveGames"—or even better—"Pilots" sitting alongside the "AddOns".

Seconded! excellent idea! In fact, maybe separate out the screenshots to their own folder too..

Post by **Micha** » Mon Apr 19, 2010 5:56 pm

While the autopackaged version of Oolite -may- be able to auto-create directories in the users' home (depending on under which user it was run), the system package (deb for Debian/Ubuntu, rpm for most others) will not be able to do this.

Best approach is probably for Oolite to auto-create the relevant directories the first time it's run.

Also, added complexity if people decide to put stuff somewhere else than the default directories...

Oolite Bulletins