Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Message-ID:	<40DBE23E.8060902@salomon.at>
Date:	Fri, 25 Jun 2004 10:28:46 +0200
From:	Michael Haubenwallner <michael DOT haubenwallner AT salomon DOT at>
User-Agent:	Mozilla Thunderbird 0.5 (X11/20040601)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	custom package server: upset finds package 'Base' from CVS/Base/setup.hint
X-Virus-Scanned:	by AMaViS perl-11

Hi,

i'm managing a custom cygwin package server and have my own packages
directly in the 'release'-subdir in CVS.

When i have checked out (cvs edit) a setup.hint file, cvs places the
original copy into CVS/Base/setup.hint. So, when i run upset, i get
a package "@ Base" in setup.{ini|bz2} with the old contents of my
setup.hint file.

My preferred solution would be one of the following:
1) hardcode into upset to skip all subdirs named 'CVS', with one
exeption: if directly in the CVS-subdir is a file named "setup.hint".
This is needed for the package 'cvs' itself, when upset is run on
a cygwin-machine, where 'cvs' is equal to 'CVS'.

2) Add a commandline-arg to give upset a list of directories not to
be searched for packages, as wildcards or regex and the ability to
define the above exception for the cvs-package, or just as an output
of a command like `find ./release -type d -print | grep 'CVS/Base'`

3) any other idea ?

thanks
    Michael
-- 
Michael Haubenwallner                    SALOMON Automation GmbH
Forschung & Entwicklung                  A-8114 Friesach bei Graz
mailto:michael DOT haubenwallner AT salomon DOT at  http://www.salomon.at

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

- Raw text -