Viktor Szakáts wrote:
>
> It won't solve the problem, since Harbour itself
> can also be installed into system dirs, where
> you cannot just store volatile configuration
> data as well.
>
> Actually this is not a Linux "thing", in most
> modern operating systems they tend to store
> programs and configuration data in separate
> areas, and this has several benefits. F.e.
> you can handle per user settings seamlessly.
> This is important on any systems which is used
> by more than one user, not to mention terminal
> servers.
>
> So the direction is to store data into '$HOME/.hbide/'
> on *nix and to store such data in '%APPDATA%\hbide\'
> dir on Windows systems.
>
> Of course it's always a good thing to allow for
> "portable" installation (f.e. on USB drives),
> where app and data resides in the same directory
> structure, and currently this is exactly what
> hbide support. The problem is that's the only
> method it supports.
>
I am ageing, so missed a point to mention in previous post.
hbIDE already supports the location of .ini files if user supplies it as
first parameter to it :
hbide.exe $HOME/_some_user_folder_/hbide.ini
For Windows I always run hbIDE from destop-icon(s) pointing to
different locations of hbide.ini.
Other files, viz., hbide.skl, hbide.scu and hbide.env inherits from
such location if not set their location explicitly.
However I never tried with %AppData% like variables, but in theory
these should be respected by OS, no.
Suggestions are welcome as to tweak this part if what I explained
above is not useful.
-----
enjoy hbIDEing...
Pritpal Bedi
http://hbide.vouch.info/
--
View this message in context:
http://n2.nabble.com/hbide-create-and-testing-package-on-Ubuntu-tp4934285p4937224.html
Sent from the harbour-devel mailing list archive at Nabble.com.
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
