App-DocKnot
view release on metacpan or search on metacpan
t/data/generate/remctl/output/readme view on Meta::CPAN
* Test::Spelling
* Test::Strict
* Test::Synopsis
All are available on CPAN. Those tests will be skipped if the modules
are not available.
To enable tests that don't detect functionality problems but are used to
sanity-check the release, set the environment variable RELEASE_TESTING
to a true value. To enable tests that may be sensitive to the local
environment or that produce a lot of false positives without uncovering
many problems, set the environment variable AUTHOR_TESTING to a true
value.
BUILDING ON WINDOWS
(These instructions are not tested by the author and are now dated.
Updated instructions via a pull request, issue, or email are very
welcome.)
First, install the Microsoft Windows SDK for Windows Vista if you have
not already. This is a free download from Microsoft for users of
"Genuine Microsoft Windows." The vcvars32.bat environment provided by
Visual Studio may work as an alternative, but has not been tested.
Next, install the MIT Kerberos for Windows SDK [1]. remctl has been
tested with version 3.2.1 but should hopefully work with later versions.
[1] https://web.mit.edu/kerberos/www/dist/index.html
Then, follow these steps:
1. Run the InitEnv.cmd script included with the Windows SDK with
parameters "/xp /release".
2. Run the configure.bat script, giving it as an argument the location
of the Kerberos for Windows SDK. For example, if you installed the
KfW SDK in "c:\KfW SDK", you should run:
configure "c:\KfW SDK"
3. Run nmake to start compiling. You can ignore the warnings.
If all goes well, you will have remctl.exe and remctl.dll. The latter
is a shared library used by the client program. It exports the same
interface as the UNIX libremctl library.
SUPPORT
The remctl web page at:
https://www.eyrie.org/~eagle/software/remctl/
will always have the current version of this package, the current
documentation, and pointers to any additional resources.
For bug tracking, use the issue tracker on GitHub:
https://github.com/rra/remctl/issues
Please be aware that I tend to be extremely busy and work projects often
take priority. I'll save your report and get to it as soon as I can,
but it may take me a couple of months.
SOURCE REPOSITORY
remctl is maintained using Git. You can access the current source on
GitHub at:
https://github.com/rra/remctl
or by cloning the repository at:
https://git.eyrie.org/git/kerberos/remctl.git
or view the repository via the web at:
https://git.eyrie.org/?p=kerberos/remctl.git
The eyrie.org repository is the canonical one, maintained by the author,
but using GitHub is probably more convenient for most purposes. Pull
requests are gratefully reviewed and normally accepted.
LICENSE
The remctl package as a whole is covered by the following copyright
statement and license:
Copyright 2015-2016, 2018 Russ Allbery <eagle@eyrie.org>
Copyright 2002-2014
The Board of Trustees of the Leland Stanford Junior University
Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:
The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Some files in this distribution are individually released under
different licenses, all of which are compatible with the above general
package license but which may require preservation of additional
notices. All required notices, and detailed information about the
licensing of each file, are recorded in the LICENSE file.
Files covered by a license with an assigned SPDX License Identifier
include SPDX-License-Identifier tags to enable automated processing of
license information. See https://spdx.org/licenses/ for more
information.
( run in 0.568 second using v1.01-cache-2.11-cpan-39bf76dae61 )