Mail Archives: cygwin/2002/02/14/15:38:00
At 03:27 PM 2/14/2002, Mack, Daemian wrote:
> > >I'd like confirmation or denial of this, because I'd like to
> > move forward
> > >without scripting a full Cygwin installation, using only
> > these three files.
> >
> > I'm not sure what you mean by a "full Cygwin installation,
> > using only these
> > three files". To people on this list, a full Cygwin
> > installation is more
> > than just the three files you indicate.
>
>*Without* scripting the full installation. From the viewpoint of my install
>package, it's infinitely easier to copy three files into a temporary working
>directory, run them, then delete them, without worrying about a full
>installation of Cygwin.
OK. If you keep yourself pointed at the temporary working directory and
no other Cygwin installation is present or loaded at the time, this should
be OK.
> > It's worth noting that the installation you're describing would be
> > considered a custom one by this list and should come with its own
> > support channel. This list can't be it. I suspect that
> > you're aware of
> > this but in case you're not, it's an important point to consider.
>
>I do realize this. What I'm asking is no more than this: is a full Cygwin
>installation required in order for bash.exe to use rsync.exe to read from
>and write to the local Windows filesystem? Or are these two files -- plus
>the cygwin.dll -- sufficient for this purpose?
Yep, should be.
Larry Hall lhall AT rfk DOT com
RFK Partners, Inc. http://www.rfk.com
838 Washington Street (508) 893-9779 - RFK Office
Holliston, MA 01746 (508) 893-9889 - FAX
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -