public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* Workflow for producing patches with cygport?
@ 2017-11-04 10:45 Matt D.
  2017-11-04 13:04 ` Jon Turney
  0 siblings, 1 reply; 3+ messages in thread
From: Matt D. @ 2017-11-04 10:45 UTC (permalink / raw)
  To: cygwin

I've gotten this far:

   download cygport
   download package src

   cd /usr/src/package*
   cygport package.cygport prep

I can now edit the source, compile, etc. But what is the workflow for 
producing a patch file of my changes?


Matt D.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 3+ messages in thread
* Re: Workflow for producing patches with cygport?
  2017-11-04 10:45 Workflow for producing patches with cygport? Matt D.
@ 2017-11-04 13:04 ` Jon Turney
  2017-11-04 13:29   ` Matt D.
  0 siblings, 1 reply; 3+ messages in thread
From: Jon Turney @ 2017-11-04 13:04 UTC (permalink / raw)
  To: The Cygwin Mailing List; +Cc: codespunk+cygwin

On 04/11/2017 10:45, Matt D. wrote:
> I've gotten this far:
> 
>    download cygport
>    download package src
> 
>    cd /usr/src/package*
>    cygport package.cygport prep
> 
> I can now edit the source, compile, etc. But what is the workflow for 
> producing a patch file of my changes?

You can use 'cygport diff' to produce a patch in ${PN}-${PVR}.${ARCH}/patch/

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 3+ messages in thread
* Re: Workflow for producing patches with cygport?
  2017-11-04 13:04 ` Jon Turney
@ 2017-11-04 13:29   ` Matt D.
  0 siblings, 0 replies; 3+ messages in thread
From: Matt D. @ 2017-11-04 13:29 UTC (permalink / raw)
  To: cygwin

Thank you.

There is no documentation for this from 'cygport --help' or 'man 
cygport'. Is this an oversight?


Matt D.

On 11/4/2017 9:04 AM, Jon Turney wrote:
> On 04/11/2017 10:45, Matt D. wrote:
>> I've gotten this far:
>>
>>    download cygport
>>    download package src
>>
>>    cd /usr/src/package*
>>    cygport package.cygport prep
>>
>> I can now edit the source, compile, etc. But what is the workflow for
>> producing a patch file of my changes?
>
> You can use 'cygport diff' to produce a patch in
> ${PN}-${PVR}.${ARCH}/patch/

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-11-04 13:29 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-11-04 10:45 Workflow for producing patches with cygport? Matt D.
2017-11-04 13:04 ` Jon Turney
2017-11-04 13:29   ` Matt D.

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).