From: vprada@corvus.com.ve
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Gentoo Installer (2) [LARGE]
Date: Sun, 2 Jun 2002 10:42:32 -0600 (MDT) [thread overview]
Message-ID: <1023036140.22900@corvus.com.ve> (raw)
In-Reply-To: <3CFA28B7.3010201@gentoo.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1359 bytes --]
Hello
The advantage of Anaconda is that is written in python. If python runs in your architecture anaconda will run in your architecture.
As i told you too, this is the first approach, now i want to modify the anaconda's code to use emerge instead or rpm.
Thanks
Víctor Prada
On Jun 02 14:16, David Chamberlain <daybird@gentoo.org> wrote:
>
> Subject: Re: [gentoo-dev] Gentoo Installer (2) [LARGE]
>
> I have no problem with the idea of an installer. The more tools the better.
> On the other hand, a possible problem with Anaconda: I haven't used it,
> but I assume it's x86 only? If so, we can't use it on ppc, sparc etc.
> One of gentoo's greatest virtues is portability (look for more ports
> appearing over the next few months), and I would encourage anyone
> writing tools to bear this in mind. For a quick fix, anaconda may be
> fine (we'll just live without the installer on ppc), but is there any
> reason why, in the long term, the --buildpkg/--usepkg features of
> portage couldn't be leveraged in place of the rpms? A virtue of this is
> that portage itself could be tweaked to enhance the installer if
> necessary, since it's our tool, not RedHat's.
>
> Regards,
>
> David
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
>
>
next prev parent reply other threads:[~2002-06-02 16:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020602122104.49479ABD9F@chiba.3jane.net>
2002-06-02 14:16 ` [gentoo-dev] Gentoo Installer (2) [LARGE] David Chamberlain
2002-06-02 14:19 ` Meir Kriheli
2002-06-02 18:22 ` Jon Nelson
2002-06-02 16:42 ` vprada [this message]
[not found] <124969252@toto.iv>
2002-06-03 18:20 ` Jeffrey D. Kowing
2002-06-03 18:36 ` Victor R. Prada
[not found] <20020602170104.57ABEAC453@chiba.3jane.net>
2002-06-02 22:18 ` David Chamberlain
2002-06-02 4:33 vprada
2002-06-02 12:18 ` foser
2002-06-02 13:03 ` Meir Kriheli
2002-06-02 12:56 ` Simonics Zsolt
2002-06-02 23:49 ` Matthew Kennedy
2002-06-03 1:22 ` William Kenworthy
2002-06-03 3:16 ` Mark Bainter
2002-06-03 12:50 ` Alexander Gretencord
2002-06-03 3:05 ` Mark Bainter
2002-06-03 3:38 ` Justin Lambert
2002-06-03 4:31 ` Matthew Kennedy
2002-06-03 5:47 ` Bjarke Sørensen
2002-06-03 14:13 ` Grant Goodyear
2002-06-03 14:57 ` Victor R. Prada
2002-06-04 1:19 ` Mark Bainter
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=1023036140.22900@corvus.com.ve \
--to=vprada@corvus.com.ve \
--cc=gentoo-dev@gentoo.org \
/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