On Oct 14 01:12, Andrew Schulman wrote:
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
Minor nit: This should be `cygport upload' to be in line with the
other cygport commands. Alternatively, cygport could introduce a
two-letter abbreviation scheme, for instance:
cygport download- cygport dl or (rcs-like) co
cygport prep- cygport pr
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
On 2014-07-07 20:14, Andrew Schulman wrote:
Using cygport, I think that packaging has become quite easy now.
That's always been my goal. :-)
Except for one thing: the upload step. Maintainers still have to go
through the procedure at
https://sourceware.org/cygwin-apps/package-upload.html.
Using cygport, I think that packaging has become quite easy now. At least,
once the cygport script is built and working, updating a package to a new
release is as easy as updating the version number in the cygport script,
then running 'cygport ... download all'.
Except for one thing: the upload
On Mon, Jul 07, 2014 at 09:14:29PM -0400, Andrew Schulman wrote:
Using cygport, I think that packaging has become quite easy now. At least,
once the cygport script is built and working, updating a package to a new
release is as easy as updating the version number in the cygport script,
then
