Re: Expand system variable in <Environment/>
Thomas Leonard <[email protected]>
| Newsgroups | gmane.comp.file-systems.zero-install.devel |
|---|---|
| Message-ID | <CAG4opy8sdhWdHP0YX-_OWMBqx-FMOx2y2tH82S8K-Y9+EvdL5w@mail.gmail.com> |
On 30 June 2015 at 15:32, Lars Kirkeskov Sørup <[email protected]> wrote: > > Hi, > > I tried to search the archive to find anything about this but failed to do so, so here goes. > > We have a runner application that runs our own bytecode. The runner is OS specific while the bytecode packages are multiplatform. > > In order to allow these packages to persist data I would like to set an enviroment variable across platforms, so these packages can remain platform independendt (and thus single release etc.) > > So, for our windows runner setting an enviroment variable to > %APPDATA%/mydir > > or on MacOS: > $HOME/Library/mydir > > but I cannot get 0install to expand system enviroment variable in value in a <Environment/> tag within an <Implementation/>. > > I have tried any syntax I could think off on Windows, e.g ${APPDATA}, $APPDATA, %APPDATA%, etc... to no avail. > > So my question is, is this at all possible? If not, is there an alternative pattern to reach the same goal or will I have to via batch/sh files to do this? Environment elements don't do expansion, but <arg> does. Depending on your language, you may be able to pass the setting as an argument. -- Dr Thomas Leonard http://roscidus.com/blog/ GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA ------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ _______________________________________________ Zero-install-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/zero-install-devel