From: "Martin Anantharaman" <Martin.Anantharaman@web.de>
To: <cygwin@cygwin.com>
Subject: cygport: How to use to build and install modified packages
Date: Fri, 15 May 2015 11:23:00 -0000 [thread overview]
Message-ID: <C1DB1AFD2EFB472D96FD43D3F1A62652@MartinsDell> (raw)
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
next reply other threads:[~2015-05-15 10:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 11:23 Martin Anantharaman [this message]
2015-05-15 14:06 ` Achim Gratz
2015-05-15 16:23 ` Achim Gratz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C1DB1AFD2EFB472D96FD43D3F1A62652@MartinsDell \
--to=martin.anantharaman@web.de \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).