public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* cygport: How to use to build and install modified packages
@ 2015-05-15 11:23 Martin Anantharaman
  2015-05-15 14:06 ` Achim Gratz
  0 siblings, 1 reply; 3+ messages in thread
From: Martin Anantharaman @ 2015-05-15 11:23 UTC (permalink / raw)
  To: cygwin

In my experimentation with run (see preceding post with subject
"run-1.3.3-1: Unicode text and empty args") I somehow managed to build a
modifed version of a released package (run-1.3.3-1) but feel I have not
found the right way of performing this task - so I ask for some advice (or
referral to some How-To?) based on how I did it:
- Get source: I did that via setup which placed the cygport-file
(run.cygport) and source-archive in /usr/src
- Unpack source: I wanted to do "cygport run prep" - but that failed to
recognize the cygwin-run-1.3.3.tar.bz2 archive and I had to do "cygport run
download" which downloaded cygwin-run-run.tar.bz2 instead. Why?
- Compile: I did "cygport run compile" to get started, then modified sources
and re-compiled (to sidestep the time-consuming configuration step) in
build/src with "make".
- Install: I thought I could install with "cygport run install" - but that
installed in the staging area within the pacakge source-tree only. So I
installed with "make install" for the time being. What is the right way,
maybe using setup after packaging the modified package?
- Package: "cygport run package" works as expect, including creating patches
- but the resulting packages (in dist) were run-run-run.tar.xz and
run-src.tar.xz - so the version is somehow getting trashed within cygport.
Does the cygport file at the outset need to be renamed to include the
version?
 
Regards, Martin


--
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: cygport: How to use to build and install modified packages
  2015-05-15 11:23 cygport: How to use to build and install modified packages Martin Anantharaman
@ 2015-05-15 14:06 ` Achim Gratz
  2015-05-15 16:23   ` Achim Gratz
  0 siblings, 1 reply; 3+ messages in thread
From: Achim Gratz @ 2015-05-15 14:06 UTC (permalink / raw)
  To: cygwin

Martin Anantharaman writes:
> In my experimentation with run (see preceding post with subject
> "run-1.3.3-1: Unicode text and empty args") I somehow managed to build a
> modifed version of a released package (run-1.3.3-1) but feel I have not
> found the right way of performing this task - so I ask for some advice (or
> referral to some How-To?) based on how I did it:
> - Get source: I did that via setup which placed the cygport-file
> (run.cygport) and source-archive in /usr/src
> - Unpack source: I wanted to do "cygport run prep" - but that failed to
> recognize the cygwin-run-1.3.3.tar.bz2 archive and I had to do "cygport run
> download" which downloaded cygwin-run-run.tar.bz2 instead. Why?

I'm using non-versioned cygport files and have patched cygport to deal
with those correctly.  The packaged cygport file should have been
run-1.3.3-1.cygport for the unpatched cygport version to work correctly.
Somehow that's not happening anymore, I'll have to see that how to
correct that.

The last "-run" is a result of the above and the "cygwin-run" at the
beginning is a result of the way cygport deals with Git repositories.
Cygport seems to prefer the versioned package file if it finds one over
the Git snapshot, I'm not sure if that's the way it should be.

> - Install: I thought I could install with "cygport run install" - but that
> installed in the staging area within the pacakge source-tree only. So I
> installed with "make install" for the time being. What is the right way,
> maybe using setup after packaging the modified package?

There is no right or wrong way, but you can just unpack into / for this
package.

> - Package: "cygport run package" works as expect, including creating patches
> - but the resulting packages (in dist) were run-run-run.tar.xz and
> run-src.tar.xz - so the version is somehow getting trashed within cygport.
> Does the cygport file at the outset need to be renamed to include the
> version?

Yes, until I can convince Yaakov to accept my patches.


Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada

--
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: cygport: How to use to build and install modified packages
  2015-05-15 14:06 ` Achim Gratz
@ 2015-05-15 16:23   ` Achim Gratz
  0 siblings, 0 replies; 3+ messages in thread
From: Achim Gratz @ 2015-05-15 16:23 UTC (permalink / raw)
  To: cygwin

Achim Gratz writes:
>> - Unpack source: I wanted to do "cygport run prep" - but that failed to
>> recognize the cygwin-run-1.3.3.tar.bz2 archive and I had to do "cygport run
>> download" which downloaded cygwin-run-run.tar.bz2 instead. Why?

…or try "cygport run.cygport prep", as the missing suffix the real
reason it does not work as intended.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

--
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:[~2015-05-15 14:06 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-05-15 11:23 cygport: How to use to build and install modified packages Martin Anantharaman
2015-05-15 14:06 ` Achim Gratz
2015-05-15 16:23   ` Achim Gratz

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).