public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Mack, Daemian" <DMack@Tickets.com>
To: "'Larry Hall (RFK Partners, Inc)'" <lhall@rfk.com>, cygwin@cygwin.com
Subject: RE: Cygwin Registry Entries and Scriptability?
Date: Thu, 14 Feb 2002 12:28:00 -0000	[thread overview]
Message-ID: <AA200D15A29A574DA33D98B75E6E5D990452EF86@syrs-mail.back.tickets.com> (raw)

> >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.
 


> 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?

Thanks for the quick response, by the way.


Daemian Mack

--
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/

             reply	other threads:[~2002-02-14 20:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-14 12:28 Mack, Daemian [this message]
2002-02-14 12:36 ` cygwin " Christopher Faylor
  -- strict thread matches above, loose matches on Subject: below --
2002-02-14 13:05 Mack, Daemian
2002-02-14 13:04 Cygwin " Mack, Daemian
     [not found] <AA200D15A29A574DA33D98B75E6E5D990452EF86@syrs-mail.back.ti ckets.com>
2002-02-14 12:36 ` Larry Hall (RFK Partners, Inc)
     [not found] <AA200D15A29A574DA33D98B75E6E5D990452EF85@syrs-mail.back.ti ckets.com>
2002-02-14 12:20 ` Larry Hall (RFK Partners, Inc)
2002-02-14 11:52 Mack, Daemian
2002-02-14 12:13 ` cygwin " Christopher Faylor
2002-02-14 12:25   ` Larry Hall (RFK Partners, Inc)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AA200D15A29A574DA33D98B75E6E5D990452EF86@syrs-mail.back.tickets.com \
    --to=dmack@tickets.com \
    --cc=cygwin@cygwin.com \
    --cc=lhall@rfk.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).