X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:mime-version
	:content-type:content-transfer-encoding; q=dns; s=default; b=BKo
	SwmmJxyZBZmuPQSBeov7kPMi507deo9qVljfweyA/hpvjH81Wmof2oi+QgQktPZN
	5FRwuKJGnFKqMijEJ2HoAfP1q3AVgMWpXcUxEBFh82p9wMgWYM6lZaxwOFxErdkL
	Vqkt8oEeaLH6Rtf2IO/REJQoiSZoKuxKlm5v/CSQ=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:mime-version
	:content-type:content-transfer-encoding; s=default; bh=HsHwwQwOw
	SNEjA0yxzXHf4bJF8w=; b=waVjJNhO3m1VzFh5pT/2OIv3fVBYcQjGhJobyWaW5
	iuLJAkyCPmx/S5DaSmfEyEdXJqDWuTub7sVM4zDiAJLL8HHpuLulXx0nMy9sZyFH
	Z2Q3gi2CyZIfZ4EN6HDXmfMS5CyCTQK9s9BGBXIQXECo5yFGIPEpg9bgMQxRVBqo
	f4=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-0.5 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2
X-HELO:	mout.web.de
From:	"Martin Anantharaman" <Martin DOT Anantharaman AT web DOT de>
To:	<cygwin AT cygwin DOT com>
Subject:	cygport: How to use to build and install modified packages
Date:	Fri, 15 May 2015 12:29:46 +0200
Message-ID:	<C1DB1AFD2EFB472D96FD43D3F1A62652@MartinsDell>
MIME-Version:	1.0
X-UI-Out-Filterresults:	notjunk:1;

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

- Raw text -