[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cygwin-apps
Subject:    Re: [RFC] cygport pm for managing package releases
From:       Andrew Schulman via Cygwin-apps <cygwin-apps () cygwin ! com>
Date:       2020-09-25 17:13:23
Message-ID: am8smf1oe0nhkav4aqmhpdv1p5u7feh5ma () 4ax ! com
[Download RAW message or body]

> I'm very keen on reducing the maintainer workload by increasing the 
> automation available to them.

Good.

> However, I'm not so sure about the approach proposed, which perpetuates 
> the 'create strange files which have a special meaning when uploaded 
> causing something non-obvious to happen' behaviour.
> 
> I think I'd perhaps rather just extend the work done with 'untest' [2] 
> to allow maintainers to do these things directly.
> 
> [2] 
> https://cygwin.com/git/?p=cygwin-apps/calm.git;a=commit;h=0a29ad572cbe1bcc64fd3624f5c38eee79c50445

I'm all in favor of using simpler methods. I just want to collect them all
in one place in cygport, so maintainers -

* don't have to remember, care, or find documentation for what the details
are for different package management functions;
* don't have to keep track as those methods change or improve;
* can rely on a stable and documented set of cygport commands to manage
their packages.

So as better automation becomes available, like the untest feature, we can
build that into cygport. But the maintainers won't necessarily have to
know; they can still just run cygport pm untest, for example.

Andrew


[prev in list] [next in list] [prev in thread] [next in thread]