diff --git a/winsup/doc/faq-api.xml b/winsup/doc/faq-api.xml index 6283fb663..eecb84000 100644 --- a/winsup/doc/faq-api.xml +++ b/winsup/doc/faq-api.xml @@ -30,13 +30,24 @@ User's Guide. Are development snapshots for the Cygwin library available? -Yes. They're made whenever anything interesting happens inside the -Cygwin library (usually roughly on a nightly basis, depending on how much -is going on). They are only intended for those people who wish to -contribute code to the project. If you aren't going to be happy -debugging problems in a buggy snapshot, avoid these and wait for a real -release. The snapshots are available from -. +Starting December 2022, the old developer snapshots have been +deprecated by regular, automated test releases. See the next FAQ entry +) + + + + +Are test releases for the Cygwin library available? + + +Yes. Starting December 2022, regular, automated test releases +are created whenever a considerable patch is pushed to the Cygwin git +repo at +. +You can download the cygwin package test releases just like any other +test release for any Cgywin package using the Cygwin Setup program. +For more info, see + diff --git a/winsup/doc/faq-programming.xml b/winsup/doc/faq-programming.xml index 6b5d28034..06dfb76f5 100644 --- a/winsup/doc/faq-programming.xml +++ b/winsup/doc/faq-programming.xml @@ -764,10 +764,10 @@ operation e.g. when checking a pointer is valid) -It is also a good -idea to use the latest code in case the bug has been fixed, so we -recommend trying the latest snapshot from - or building the DLL from git. +It is also a good idea to use the latest code in case the bug has been fixed, +so we recommend trying the latest cygwin test release (see +) +or building the DLL from git. To build a debugging version of the Cygwin DLL, you will need to follow diff --git a/winsup/doc/faq-setup.xml b/winsup/doc/faq-setup.xml index da9fce534..981a7246a 100644 --- a/winsup/doc/faq-setup.xml +++ b/winsup/doc/faq-setup.xml @@ -21,10 +21,10 @@ tools. is available on using the Cygwin Setup program. If you do it any other way, you're on your own! -If something doesn't work right for you, and -it's not covered here or in the latest development snapshot at -, then by all means report it to the -mailing list. +If something doesn't work right for you, and it's not covered here or in +the latest Cygwin test package (see +), +then by all means report it to the mailing list. For a searchable list of packages that can be installed with Cygwin, see . @@ -627,56 +627,35 @@ directory has been stored in the registry at all. - -How do I install snapshots? + +How do I install Cygwin test releases? -First, are you sure you want to do this? Snapshots are risky. They -have not been tested. Use them only if there is a feature or -bugfix that you need to try, and you are willing to deal with any -problems, or at the request of a Cygwin developer. +You can install Cygwin test releases just like test releases of +any other package using the Cygwin Setup program. Ideally, you install +not only the cygwin test package, but +also the cygwin-debuginfo test package +with the same version number. The cygwin-debuginfo package allows source +code debugging using gdb. Install the +cygwin-devel test package, if you also +want to test building against a new API. -You cannot use the Cygwin Setup program to install a snapshot. +However, are you sure you want to do this? Test releases are risky. +They have only been marginally tested most of the time. Use them +only if there is a feature or bugfix that +you need to try, and you are willing to deal with any problems, or at the +request of a Cygwin developer. -First, you will need to download the snapshot from the snapshots -page at . Note the directory where -you saved the snapshot tarball. - -Before installing a snapshot, you must first Close all Cygwin -applications, including shells and services (e.g., inetd, sshd). -You will not be able to replace cygwin1.dll if any Cygwin process is -running. You may have to restart Windows to clear the DLL from memory -(beware of automatic service startup). - -Most of the downloaded snapshot can be installed using tar. Cygwin -tar won't be able to update /usr/bin/cygwin1.dll (because it's -used by tar itself), but it should succeed with everything else. If -you are only installing the DLL snapshot, skip the first tar command. Open -a bash shell (it should be the only running Cygwin process) and issue -the following commands: - - /bin/tar -C / -xvf /posix/path/to/cygwin-inst-YYYYMMDD.tar.* --exclude=usr/bin/cygwin1.dll - /bin/tar -C /tmp -xvf /posix/path/to/cygwin-inst-YYYYMMDD.tar.* usr/bin/cygwin1.dll - - -Exit the bash shell, and use Explorer or the Windows command shell to -first rename C:\cygwin\bin\cygwin1.dll to -C:\cygwin\bin\cygwin1-prev.dll and then move -C:\cygwin\tmp\usr\bin\cygwin1.dll -to C:\cygwin\bin\cygwin1.dll (assuming you installed Cygwin in -C:\cygwin). - -The operative word in trying the snapshots is "trying". If you -notice a problem with the snapshot that was not present in the release -DLL (what we call a "regression"), please report it to the Cygwin -mailing list (see for problem -reporting guidelines). If you wish to go back to the older version of the -DLL, again, close all Cygwin processes, delete -C:\cygwin\bin\cygwin1.dll, and -rename C:\cygwin\bin\cygwin1-prev.dll back to -C:\cygwin\bin\cygwin1.dll (again assuming that your "/" is -C:\cygwin). To restore the rest of the snapshot -files, reinstall the "cygwin" package using the Cygwin Setup program. +The operative word in trying the test releases is +"trying". If you notice a problem with the snapshot +that was not present in the release DLL (what we call a "regression"), +please report it to the Cygwin mailing list +(see for problem +reporting guidelines). If you wish to go back to the most recent non-test +release of the Cygwin DLL, close all Cygwin processes, as usual, start the +Cygwin Setup program and choose the most recent non-test release of the +cygwin package, as well as the cygwin-debuginfo and cygwin-devel packages. +That's all there is to it.