#18 psotnic path

[patrick]

I think we should save the path of psotnic directory in config.h

Now depending on how you start psotnic, the userlist and all other files which are created (e.x. by modules) will be saved on different places.

For example if you started it with ./psotnic, the files will be saved in bin/ (non-binaries in bin/? :p)

And if you start the bot with bin/psotnic (like i usually do) the files are in ../bin/ - also .update stores the new binary there and not in bin/ directory.

Maybe also move source files to src/ then.

What do you think?

At least I need a way to find the modules/ directory (no matter how you started the bot)

[nukleus]

Logged In: YES
user_id=1352625
Originator: NO

thats one thing i wanted to achieve with my patch adding install targets: it added default patchs for binary, config and modules files. You told me that no one wants to install it, so i stopped. next thing would've been making psotnic loading everything from the default paths, so stuff like loading modules or userlist would first look in the predefined dir if it is present, and then try the patch given in cfg.
Example:
.load vctrl (or .load vctrl.so) would first look in $MODULES_DIR, and if not found ./
the code to search the file could easily reside in functions.cpp.

[nukleus]

Logged In: YES
user_id=1352625
Originator: NO

thats one thing i wanted to achieve with my patch adding install targets: it added default patchs for binary, config and modules files. You told me that no one wants to install it, so i stopped. next thing would've been making psotnic loading everything from the default paths, so stuff like loading modules or userlist would first look in the predefined dir if it is present, and then try the patch given in cfg.
Example:
.load vctrl (or .load vctrl.so) would first look in $MODULES_DIR, and if not found ./
the code to search the file could easily reside in functions.cpp.