I've recently just added a feature to autopackage (and PTK) so that '@import'
files can now automatically be loaded from somewhere other than the COPKG
folder.
It now searches the following directories for the file:
%APPDATA%\etc
=> c:\users\<user>\AppData\Roaming\etc\<filename>
%LOCALAPPDATA%\etc
=> c:\users\<user>\AppData\Local\etc\<filename>
%ALLUSERSPROFILE%\etc
=> c:\programdata\etc\<filename>
then it tries to find the file in the current directory and walks it's way up
the directory tree to find it.
So if you are working in c:\projects\coapp\zlib\COPKG\ it will look for :
c:\projects\coapp\zlib\COPKG\<filename>
c:\projects\coapp\zlib\<filename>
c:\projects\coapp\<filename>
c:\projects\<filename>
c:\<filename>
It will grab the first one it finds in that order.
The CoApp package will now install an
outercurve.inc
file in
%ALLUSERSPROFILE%\etc
So that we don't have to put outercurve.inc into every single shallow fork, and
it can still be referenced with
@import "outercurve.inc";
====
The other benefit, is that you can put in a custom file in your %APPDATA%\etc
folder, and it will use that first (so if you want local customizations, you
don't have to do painful workarounds)
===
Oh, and it also tries (but won't complain on fail) to import a <file>.user for
any file that it's loading-- so when you have :
c:\projects\coapp\zlib\COPKG\zlib.autopkg
you can have a file called
c:\projects\coapp\zlib\COPKG\zlib.autopkg.user
And it will get auto-included (so you can have local settings that will get
automatically loaded.
This also means that you can have a .buildinfo.user file as well!
Garrett
_______________________________________________
Mailing list: https://launchpad.net/~coapp-developers
Post to : coapp-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~coapp-developers
More help : https://help.launchpad.net/ListHelp
