From: "Gerrit P. Haase" <gerrit.haase@t-online.de>
To: cygwin@cygwin.com
Subject: Re: where to find nslookup for Cygwin?
Date: Tue, 19 Dec 2000 04:35:00 -0000 [thread overview]
Message-ID: <3A3F649A.19216.3C8B824@localhost> (raw)
In-Reply-To: <20001219124501.A291@OOPS.ip6seguridad.com>
<19 Dec 2000, 12:45 Uhr wars, als Pablo Ruiz Garcia folgendes schrub:>
< Re: where to find nslookup for Cygw >
>
> Actually there is some similar to a "distro", this is what
> cygwin setup installs, and all the installed files are listed on
> /etc/setup/*. RPM is good enought to make *contribution* packages,
> probable better than tar+gz, and tar+bz2, but by now RPM
> is not part of the official-cygwin-release/distro
> it makes me dont want rpm to be on /usr instead of /usr/local.
I think, it is no problem, to include the sources of tar and gzip in
the setup.exe, and it would be much more work, to use rpm.
Like it is, it works fine.
tar+gz and tar+bz2 are much more standard than other pack-mechanisms.
Ciao,
--
=^..^=
Gerrit Peter Haase
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2000-12-19 4:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-19 3:43 Pablo Ruiz Garcia
2000-12-19 4:23 ` Corinna Vinschen
2000-12-19 4:35 ` Gerrit P. Haase [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-12-17 11:57 Jari Aalto
2000-12-17 13:50 ` Corinna Vinschen
2000-12-17 14:52 ` Stephen C. Biggs
2000-12-17 15:13 ` Corinna Vinschen
2000-12-17 18:47 ` Stephen C. Biggs
2000-12-17 19:31 ` Chris Abbey
2000-12-17 20:44 ` Charles S. Wilson
2000-12-17 20:51 ` Stephen C. Biggs
2000-12-17 21:24 ` Chris Abbey
2000-12-18 0:44 ` Corinna Vinschen
2000-12-18 23:36 ` Stephen C. Biggs
2000-12-19 2:53 ` Corinna Vinschen
2000-12-19 3:24 ` Stephen C. Biggs
2000-12-19 4:07 ` Corinna Vinschen
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=3A3F649A.19216.3C8B824@localhost \
--to=gerrit.haase@t-online.de \
--cc=cygwin@cygwin.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).