public inbox for gentoo-installer@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andrew Gaffney <agaffney@skylineaero.com>
To: gentoo-installer@lists.gentoo.org
Subject: Re: [gentoo-installer] a few different questions
Date: Mon, 02 Feb 2004 08:06:14 -0600	[thread overview]
Message-ID: <401E5956.6090301@skylineaero.com> (raw)
In-Reply-To: <20040202140011.GV22870@mail.lieber.org>

Kurt Lieber wrote:
> Have you read the requirements doc that esammer put together?  It answers
> many/most of your questions.
> 
> http://dev.gentoo.org/~esammer/gli/gentoo_installer.txt
> http://dev.gentoo.org/~esammer/gli/gli_uml.png
> http://dev.gentoo.org/~esammer/gli/gli_use_case.png

That first doc was especially informative. I'd seen the last two, but not the first.

> On Mon, Feb 02, 2004 at 07:16:27AM -0600 or thereabouts, Andrew Gaffney wrote:
> 
>>1. I've heard that the core installer will be written in Python. Is this 
>>true?
> 
> That's the current plan, yes.
> 
>>2. Whether Python or not, will real-time frontends have to be written the 
>>same language as the core installer,
> 
> No.
> 
>>3. Will the core installer have plugin capabilities (e.g. user-created 
>>configuration/installation steps), either scripted (bash) or coded (Python 
>>or whatever)?
> 
> Not sure, but I don't think it's currently planned to have a plugin
> interface for the back end.

For example, with the current CVS version of GLIS, you can create bash scripts that the 
installer will run before or after certain steps in the install process. Even if seldom 
used, it would be a handy (and easy to code) feature of GLI.

>>4. Which existing installer will the new code be based from or will this be 
>>done completely from scratch possibly using existing concepts?
> 
> from scratch.
> 
>>5. Are there any plans to include X along with Qt, GTK, Tcl/Tk, etc. on the 
>>LiveCD to allow for the creation of GUI installer frontends?
> 
> haven't got that far yet.
> 
>>6. What is already done? What needs to be done? What is still up in the air?
> 
> See the docs.
> 
>>7. How can I help? I don't know Python, but I have pretty decent bash - 
>>only since working on GLIS frontend ;) - and Perl skills. I don't know any 
>>Python, but I can always learn.
> 
> See the docs.
> 
>>8. Anything else important that I might have missed?
> 
> Yes.  See the docs. ;)

Alright, I get the point ;)

-- 
Andrew Gaffney
System Administrator
Skyline Aeronautics, LLC.
776 North Bell Avenue
Chesterfield, MO 63005
636-357-1548


--
gentoo-installer@gentoo.org mailing list


  reply	other threads:[~2004-02-02 14:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-02 13:16 [gentoo-installer] a few different questions Andrew Gaffney
2004-02-02 14:00 ` Kurt Lieber
2004-02-02 14:06   ` Andrew Gaffney [this message]
2004-02-03  3:37 ` Eric Sammer
2004-02-03  3:46   ` Andrew Gaffney
2004-02-03  4:13     ` Eric Sammer
2004-02-03 10:22       ` Paul de Vrieze
2004-02-03 16:59         ` Eric Sammer

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=401E5956.6090301@skylineaero.com \
    --to=agaffney@skylineaero.com \
    --cc=gentoo-installer@lists.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