Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Mike McDonald <mikemac@mikemac.com>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: Cross compiling RPMs
Date: Sun, 28 Jan 2001 09:45:39 -0800	[thread overview]
Message-ID: <200101281745.JAA25600@saturn.mikemac.com> (raw)
In-Reply-To: Your message of "Sun, 28 Jan 2001 04:10:26 PST." <20010128041025.C4287@bacchus.dhis.org>


>Date: 	Sun, 28 Jan 2001 04:10:26 -0800
>From: Ralf Baechle <ralf@oss.sgi.com>
>To: Mike McDonald <mikemac@mikemac.com>
>Subject: Re: Cross compiling RPMs
>
>On Sat, Jan 27, 2001 at 02:57:24PM -0800, Mike McDonald wrote:
>
>>   I was thinking of what the MINIMUM set of RPMs you needed installed
>> so you could bootstrap a system up from sources, not what's the
>> minimum needed to recompile any arbitrary RPM.
>
>Really depends on what you want to do.  Many packages detect other packages
>or features of other packages.  This builds a big evil network of
>dependencies which make bootstrapping somewhat hard.  It's a good idea to
>start with an as complete installation as possible.

  I want to do just the opposite. I want to start with the minimum set
of installed binaries and build a complete binary distribution from
its sources. (That means finding the root of the dependency graph and
starting there, assuming there actually is one. It isn't necessarily a
single rpm. People like to make circular dependancies!)

  Mike McDonald
  mikemac@mikemac.com

  reply	other threads:[~2001-01-28 17:46 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-26 18:15 Cross compiling RPMs Mike McDonald
2001-01-26 18:37 ` Pete Popov
2001-01-26 19:27   ` Mike McDonald
2001-01-26 19:39     ` Pete Popov
2001-01-26 19:47       ` Mike McDonald
2001-01-26 20:23   ` Florian Lohoff
2001-01-26 20:51     ` Jun Sun
2001-01-26 21:11       ` Mike McDonald
2001-01-27  0:31         ` Pete Popov
2001-01-26 21:14     ` Mike McDonald
2001-01-27 10:52       ` Karel van Houten
2001-01-27 10:52         ` Karel van Houten
2001-01-27 22:57         ` Mike McDonald
2001-01-28 12:10           ` Ralf Baechle
2001-01-28 17:45             ` Mike McDonald [this message]
2001-01-29  0:05               ` Ralf Baechle
2001-01-29 15:23               ` Maciej W. Rozycki
2001-01-27  7:42     ` Maciej W. Rozycki
2001-01-27 18:50       ` Ralf Baechle
2001-01-28 18:30         ` Geert Uytterhoeven
2001-01-28 19:46           ` Pim van Riezen
2001-01-28 19:46             ` Pim van Riezen
2001-01-29  0:02           ` Ralf Baechle
2001-01-29  8:44             ` Geert Uytterhoeven
2001-01-29 21:54               ` Ralf Baechle
2001-01-29 15:57         ` Maciej W. Rozycki
2001-01-30  0:12           ` Mike McDonald
2001-01-30  9:46             ` Maciej W. Rozycki
2001-01-28 18:27     ` Geert Uytterhoeven
2001-01-26 20:28 ` Jun Sun

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200101281745.JAA25600@saturn.mikemac.com \
    --to=mikemac@mikemac.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=ralf@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox