/home/Yaakov/src/cygport/tests/cygport-0.20.2-1.noarch/src/cygport-0.20.2/lib/pkg_upload.cygpart

Cygport Reference Manual

### TABLE OF CONTENTS

- Uploading

## Uploading

[ Top ] [ Chapter 13 ] [ Concepts ]

INTRODUCTION

Once your binary and source packages are built, in order to distribute them to users you'll need to upload them to the Cygwin package archive. Before you can upload packages, you'll need to do the following things:

- Request upload privileges, and provide your ssh public key. The Uploading Packages page tells how to do that, and how to be notified in case of problems with your uploads.
- After your key is approved, connect once to cygwin.com by `sftp cygwin@cygwin.com`. Verify that the host key fingerprint for cygwin.com matches one of the ones posted on the Uploading Packages page. If it does, answer "yes" to continue connecting. Then exit sftp. This will store the host key fingerprint in your ~/.known_hosts file. You have to do this once before uploading, or the upload will fail.
- Be listed on the Cygwin package maintainers list as the maintainer of your packages. Ask on the cygwin-apps mailing list if you need help getting listed.

Once those things are done, running `cygport upload` (or `cygport up` for short) will upload your finished packages to the package archive on cygwin.com. From there, if everything goes well, the new files should appear on your local Cygwin mirror within about 12 hours.