X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.5 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,TW_YG
X-Spam-Check-By: sourceware.org
Message-ID: <4F5FF2ED.6010905@users.sourceforge.net>
Date: Tue, 13 Mar 2012 20:22:53 -0500
From: "Yaakov (Cygwin/X)" <yselkowitz AT users DOT sourceforge DOT net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: cygport/setup questions
References: <87mx7kutlc DOT fsf AT Rainer DOT invalid>
In-Reply-To: <87mx7kutlc.fsf@Rainer.invalid>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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

On 2012-03-13 15:35, Achim Gratz wrote:
> 1. Is there some way to specify CPAN bundles rather than individual
> packages in the .cygport file?  I don't mind if I'll get a tar.bz for
> each package the bundle pulls in, I just want to limit the number of
> packages visible during setup.

Not simply.  A CPAN bundle doesn't contain more than a pod file; it 
relies on CPAN to install whatever modules it requires.  There is also 
no guarantee that a given module is not a member of more than one 
bundle, which would result in file clobbering, and setup.exe does not 
handle that gracefully.

If you just want to make it easier for users to install a CPAN bundle, I 
suggest packaging each module individually, then have the bundle package 
depend on the other modules.

> 2. How should I name a package that I patch locally?  Can I use a
> non-numerical RELEASE, I'd like to avoid name clashes between the patched
> package and later official releases.

IIRC, release must begin with a digit.  Perhaps a 0.x release number 
would work, I haven't tried it.

> For the patch itself, I just edit the sources, that cygport is going to
> build from.  Do I have to (re-)generate the src.patch before each build
> or is cygport doing that by itself?

Once I've created a patch, I copy that patch alongside the .cygport, 
give it a meaningful name, then add it to PATCH_URI.  That makes it 
easier to carry the patch forward from one version/release to another.

> 3. How can I make sure that local customizations are always done after
> all "real" package installs?  It seems there is a hidden category
> _PostInstallLast that may or may not do that.  Also, I might need to
> control the order of post-install scripts, they seem to be run in
> alphabetical order, can I rely on that?

What local customizations do you want?

> 4. From the testing results so far, I will always have to do a rebaseall
> and perlrebase.  Can I do this from setup.exe (after customization) or
> does it have to be a separate process after setup.exe has finished?

The eventual goal is to integrate this into setup.exe, but currently 
these need to be run manually after installation/update.


Yaakov

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