This is the mail archive of the
mailing list for the Cygwin project.
Re: Portable shell code between Cygwin and Linux
- From: "Sebastien Vauban" <wxhgmqzgwmuf at spammotel dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 01 Aug 2011 08:49:12 +0200
- Subject: Re: Portable shell code between Cygwin and Linux
- References: <email@example.com> <20110729201651.GB13084@calimero.vinschen.de> <firstname.lastname@example.org>
Andrey Repin wrote:
>>> For every shell code that I write, I'd like it to be portable both to
>>> Cygwin on Windows, and to Ubuntu Linux for example.
>>> It's kinda possible, but am blocked with such a use case:
>>> alias vpnup='exec sudo openvpn --config ~/config/client.vpn --writepid /tmp/openvpn.pid &'
>>> While this worked perfectly under Ubuntu, I've had to make up a customized
>>> version for Windows:
>>> alias vpnupwin='cd c:/home/sva/config; openvpn --config client.vpn --writepid c:/cygwin/tmp/openvpn.pid &'
>> Don't use Win32 paths. Use POSIX paths:
>> alias vpnupwin='cd /cygdrive/c/home/sva/config; openvpn --config client.vpn --writepid /cygdrive/c/cygwin/tmp/openvpn.pid &'
> Moreover, the very first line is wrong.
> Must be
> alias vpnup='exec sudo openvpn --config $HOME/config/client.vpn --writepid /tmp/openvpn.pid &'
> that's where his problem began, IMO.
That's interesting. I thought this was completely equivalent (~ or $HOME), and
preferred the shorter version.
But you say it's not. Can you comment on this? Thanks in advance...
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple