Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps AT cygwin DOT com Delivered-To: mailing list cygwin-apps AT cygwin DOT com content-class: urn:content-classes:message Subject: RE: info: single install xfree86 + minimal cygwin? MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 10 Apr 2002 10:00:17 +1000 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Robert Collins" To: "Ian Burrell" , Cc: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g3A02U409427 > -----Original Message----- > From: Ian Burrell [mailto:iburrell AT znark DOT com] > Sent: Wednesday, April 10, 2002 9:49 AM > Is it possible to have multiple packages in a subdirectory and > setup.hint file? Or does each package needs its own directory? Each package needs it's own directory. > For a > hierarchy, I was thinking: base, devel, doc, fonts, and progs > (for the > optional servers). I'm not clear not the hierarchy there - that reads like a list to me. You've got two clauses you can independently use to make a hierarchy and package dependencies - category:(i.e. the devel tarball belongs in XFree86 and in Devel) and requires: (i.e. the server package requires the fonts and the programs and ...) > There are a couple of refinements that can be made to the > repackaging. > First, the 75dpi fonts make up the bulk (10MB) of the fonts > package and > aren't strictly required. They could be made their own package. The > miscellaneous fonts could be folded into the base package so there is > only one required package. > > Second, move the man3 man pages into the devel package. Also, > move the > .a files in /usr/X11R6/lib into devel. That reduces the base > package by > a couple MB. Those refinements can be made at any point - there's no need to have it perfect on first release. Setup.exe is quite capable of handling files moving from one package to another now. Rob