Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-apps-owner AT cygwin DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT cygwin DOT com>
List-Help: <mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
Message-ID: <008101c1a84c$787292c0$0d00a8c0@mchasecompaq>
From: "Michael A Chase" <mchase AT ix DOT netcom DOT com>
To: "Cygwin-Apps" <cygwin-apps AT sources DOT redhat DOT com>
References: <052f01c1a735$e7e4ee90$0200a8c0 AT lifelesswks>
Subject: Re: base-files package needs a maintainer
Date: Mon, 28 Jan 2002 14:34:47 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

Shouldn't this be part of the ash package?  Now that it's part of the Base
category, there shouldn't be any problem creating /etc/profile when ash is
installed.
--
Mac :})
** I normally forward private questions to the appropriate mail list. **
Ask Smarter: http://www.tuxedo.org/~esr/faqs/smart-questions.htm
Give a hobbit a fish and he eats fish for a day.
Give a hobbit a ring and he eats fish for an age.
----- Original Message -----
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: <cygwin-apps AT sources DOT redhat DOT com>
Sent: Sunday, January 27, 2002 05:24
Subject: base-files package needs a maintainer


> Setup.hint:
> @ base_files
> sdesc: "Core common files needed for correct operation of cygwin"
> category: Base
>
> The entire package is attached.
>
> The /etc/profile generation is getting removed from setup.exe unless
> someone provides a _real good_ reason for it to remain.
>
> Setup.exe should be *data driven*, and in this area is not at the
> moment.
>
> This package can be released at any point, it shouldn't cause any
> problem with current setup.exe's, and will allow a future release of
> setup.exe to do away with the /etc/profile generation crud.