This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: cygport upload command?
- From: Andrew Schulman <schulman dot andrew at epa dot gov>
- To: cygwin-apps at cygwin dot com
- Date: Tue, 14 Oct 2014 01:12:55 -0400
- Subject: Re: cygport upload command?
- Authentication-results: sourceware.org; auth=none
- References: <slgmr9ha3gt7le8n3fq6i3cdin8m619phj at 4ax dot com> <slgmr9ha3gt7le8n3fq6i3cdin8m619phj-e09XROE/p8c at public dot gmane dot org> <53BB91AB dot 1020507 at cygwin dot com>
> On 2014-07-07 20:14, Andrew Schulman wrote:
> > Yaakov, would you consider adding an 'upload' command to cygport, that
> > would handle the uploading details? That would take away the last bit of
> > manual work in a routine package update.
>
> I'm a bit busy at the moment, but it sounds like a good idea to me.
I have an implementation of this ready at
https://github.com/andrex-e-schulman/cygport. What's new compared to
upstream git:
* New upload command (cygport up).
* Documented upload command in manuals and README.
* Currently only one upload client, lftp, is supported. I've tested the
implementation a good bit, and it works well as long as there's no trouble,
i.e. lftp can connect to sftp://cygwin.com. If it can't connect, then you
get told "max-retries exceeded" and "Upload failed", which doesn't help at
all to figure out why the upload failed (can't connect, can't authenticate,
...). Unfortunately, it's hard to make lftp give much better information.
* Simple API for adding support for other upload clients. The API is
described in pkg_upload.cygpart. I'm planning to add support for sftp and
rsync soon, and I hope it will be easier to get useful failure information
from them if the upload fails.
Please let me know if you have any comments or would like to see any
changes.
Andrew