X-Spam-Check-By: sourceware.org Date: Sun, 11 Jun 2006 14:31:59 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: RPM's (was Re: unix 'at' command implementation) Message-ID: <20060611183159.GE12755@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <061020062022.10945.448B29F200067FE000002AC122068246930A050E040D0C079D0A@comcast.net> <448B643D.6040401@tlinx.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 On Sun, Jun 11, 2006 at 02:04:11PM -0400, Igor Peshansky wrote: >Technically, nothing prevents you from shipping a Cygwin package (which is >just a .tar.bz2) that contains only the Cygwin binary RPM and the >postinstall script that invokes "rpm" to unpack that binary RPM (as long >as that package also "requires:" the "rpm" package). You'll also need to >build a manifest of all extracted files and have a preremove script that >cleans those up. See the gcc-mingw-core package for an example of a >similar approach. Nothing would stop anyone from using rpm to build a package and then using "rpm2tar" to convert the rpm to a .tar.bz2 file either. cgf -- 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/