PlaneteCasio
/
libc
1
0
Fork 0
Code Issues 6 Pull Requests Releases Wiki Activity

Add FAQ about old packages. Remove B20 references.

This commit is contained in:
Joshua Daniel Franklin 2004-03-17 17:39:44 +00:00
parent 12d545fb65
commit 1c5695b698
1 changed files with 40 additions and 36 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

76
winsup/doc/install.texinfo
View File

@ -1,59 +1,61 @@
@chapter Installation Instructions
@section Contents
Unlike previous net releases such as B20.1 and earlier, there is no
monolithic "full" or "usertools" installation. Rather, you can pick and
choose the packages you wish to install, and update them individually.
There is only one recommended way to install Cygwin, which is to use the GUI
installer ``Cygwin Setup''. It is flexible and easy to use.
You can pick and choose the packages you wish to install, and update
them individually. Full source code is available for all packages and
tools. More information on using Cygwin Setup may be found at
@file{http://cygwin.com/cygwin-ug-net/setup-net.html}.
If you do it any other way, you're on your own! That said, keep in mind
that the GUI installer is a "work in progress", so there might be a few
difficulties, especially if you are behind a firewall or have other
specific requirements. If something doesn't work right for you, and
it's not covered here or in the latest development snapshot at
@file{http://cygwin.com/setup-snapshots/}, then by all means report it to the
mailing list.
For a searchable list of packages that can be installed with Cygwin,
see @file{http://cygwin.com/packages/}.
Full source code is available for all packages and tools.
There is only one recommended way to install Cygwin, which is to use the GUI
installer ``Cygwin Setup''. It is flexible and easy to use.
Do it any other way, and you're on your own! That said, keep in mind
that the GUI installer is a "work in progress", so there might be a few
difficulties, especially if you are behind a firewall or have other
specific requirements. If something doesn't work right for you, and
it's not covered here or elsewhere, then by all means report it to the
mailing list.
@section Installation using ``Cygwin Setup''
The Cygwin Setup program is the @emph{only} recommended way to install
Cygwin.
Cygwin.
@subsection Why not install in C:\?
The Cygwin Setup program will prompt you for a "root" directory.
The default is @samp{C:\cygwin}, but you can change it. You are urged not to
choose something like 'C:\' (the root directory on the system drive) for
choose something like @samp{C:\} (the root directory on the system drive) for
your Cygwin root. If you do, then critical Cygwin system directories
like 'etc', 'lib' and 'bin' could easily be corrupted by other (non-Cygwin)
applications or packages that use \etc, \lib or \bin. Perhaps there is
no conflict now, but who knows what you might install in the future?
It's also just good common sense to segregate your Cygwin "filesystems"
from the rest of your Windows system disk.
like @samp{etc}, @samp{lib} and @samp{bin} could easily be corrupted by
other (non-Cygwin) applications or packages that use @samp{\etc},
@samp{\lib} or @samp{\bin}. Perhaps there is no conflict now, but who
knows what you might install in the future? It's also just good common
sense to segregate your Cygwin "filesystems" from the rest of your
Windows system disk.
(In the past, there had been genuine bugs that would cause problems
for people who installed in C:\, but we believe those are gone now.)
for people who installed in @samp{C:\}, but we believe those are gone
now.)
@subsection Can I use Cygwin Setup to update a B18, B19, B20, B20.1 or CD-ROM (1.0) installation of Cygwin?
@subsection Can I use Cygwin Setup to get old versions of packages (like gcc-2.95)?
No, you must start from scratch with the new Cygwin Setup. The
overall structure has changed so much that it would be pointless to
try to accomodate old installations of Cygwin. You will probably be
much better off with a whole new installation anyway. You may backup
or rename your old installation first, or just install the new one
somewhere else. Be sure to make note of your current mount table,
because this will be overwritten during the new setup. Make sure you
don't end up with two different versions of @samp{cygwin1.dll} on your
system.
Cygwin Setup can be used to install any packages that are on a
Cygwin mirror, which usually includes one version previous to the
current one. The complete list may be searched at
@file{http://cygwin.com/packages/}. There is no complete archive of
older packages. If you have a problem with the current version of
a Cygwin package, please report it to the mailing list using the
guidelines at @file{http://cygwin.com/problems.html}.
Once you've installed the latest net release, Cygwin Setup will update
just the individual packages that need it.
That said, if you really need an older package, you may be able to find
an outdated or archival mirror by searching the web for an old package
version (for example, @samp{gcc2-2.95.3-10-src.tar.bz2}), but keep in
mind that this older version will not be supported by the mailing list
and that installing the older version will not help improve Cygwin.
@subsection Is Cygwin Setup, or one of the packages, infected with a virus?
@ -276,5 +278,7 @@ to @code{C:\cygwin\bin\cygwin1.dll}.
NO. Cygwin Setup cannot do this for you. Use a tool designed for
this purpose. See @file{http://rsync.samba.org/},
@file{http://sunsite.org.uk/packages/mirror/},
@file{http://wget.sunsite.dk/} for utilities that can do this for you.
For more information on setting up a custom Cygwin package server, see
the Cygwin Setup homepage at
@file{http://sources.redhat.com/cygwin-apps/setup.html}.