X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Message-ID: <4718B2C1.2090308@byu.net> Date: Fri, 19 Oct 2007 07:36:01 -0600 From: Eric Blake User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.6) Gecko/20070728 Thunderbird/2.0.0.6 Mnenhy/0.7.5.666 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: [ANNOUNCEMENT] Updated: bash-3.2.25-17 References: <20071019080115.GF20400@calimero.vinschen.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Igor Peshansky on 10/19/2007 7:29 AM: >> Why not create a stand-alone package in the base category which >> consists of just the postinstall script? > > I could, but the issue is more basic than where the script lives. Right > now Cygwin populates the /dev directory as a virtual directory within the > DLL. The script I'm talking about will make /dev a real directory, and > the only thing Cygwin will deal with is devices. > > What the transition would entail is not clear to me. But the bash postinstall script already creates /dev as a real directory, as of my release announcement; it just isn't very populated. I think making the script its own package in base, then making bash depend on that package, would be worthwhile. - -- Don't work too hard, make some time for fun as well! Eric Blake ebb9@byu.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHGLLB84KuGfSFAYARAiQ9AKDZny1eTSyCP9dKKLjRzrj+iBO0GACeP2oy As9WTODJsVbFc4T/vlEc3Ro= =DaVD -----END PGP SIGNATURE----- -- 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/