From: Donnie Berkholz <spyderous@gentoo.org>
To: gentoo-desktop-research@lists.gentoo.org
Subject: Re: [gentoo-desktop-research] Installer
Date: Thu, 22 Jan 2004 12:02:51 -0500 [thread overview]
Message-ID: <1074790970.1942.6.camel@localhost> (raw)
In-Reply-To: <m2n08g72of.fsf@krotkine.idm.fr>
[-- Attachment #1: Type: text/plain, Size: 1207 bytes --]
On Thu, 2004-01-22 at 04:28, dams@gentoo.org wrote:
> you are probably right on the installer part : it's maybe too big for the
> -research to develop it. But I think it's still a good thinkg to talk about it,
> with logs, meeting reports and so on. It might be good to have at least
> organized and written notes on the subject, even if we don't bring anything
> new. Installer development should not be held by the -research imo, but
> Installer research can be :)
Oh you of little faith. Someone approached karltk at LWE with a
completed python+gtk2 installer. See http://pen2.sclab.clarkson.edu/.
I quote Karl:
"What's more, they're going to be working actively on this
irrespectively of whether we officially start using it or not. I
personally would think it completely stupid not to seriously consider
this most generous offer; they are an entire sw development team, they
seem organised, they have api docs, and they're long-time gentoo users.
Having them do most of the dirty-work, leaves us to do integration and
tweaks, to polish this thing off."
An old snapshot of source is at:
http://www.clarkson.edu/class/cs450/fa2003/projects/gentoo/pen2.tar.gz.
Thanks,
Donnie
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-22 17:02 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 8:54 [gentoo-desktop-research] Report of the desktop-research meeting Paul de Vrieze
2004-01-20 9:12 ` Mario Udina
2004-01-20 10:11 ` Paul de Vrieze
2004-01-20 10:40 ` foser
2004-01-20 10:48 ` Tiemo Kieft
2004-01-20 12:23 ` Donnie Berkholz
2004-01-20 13:47 ` foser
2004-01-20 14:21 ` Donnie Berkholz
2004-01-20 17:53 ` Brandon Hale
2004-01-20 19:33 ` dams
2004-01-20 19:36 ` dams
2004-01-21 0:07 ` foser
2004-01-20 19:39 ` Joe McCann
2004-01-21 10:06 ` dams
2004-01-20 12:55 ` Paul de Vrieze
2004-01-20 14:00 ` foser
2004-01-20 17:30 ` Tom Hosiawa
2004-01-21 19:57 ` Seemant Kulleen
2004-01-21 20:01 ` Donnie Berkholz
2004-01-21 22:58 ` foser
2004-01-22 0:13 ` Alastair Tse
2004-01-22 9:11 ` dams
2004-01-22 9:25 ` dams
2004-01-22 9:28 ` dams
2004-01-22 17:02 ` Donnie Berkholz [this message]
2004-01-22 17:47 ` [gentoo-desktop-research] Installer Tiemo Kieft
2004-01-22 20:45 ` Paul de Vrieze
2004-01-22 18:38 ` Scott Koch
2004-01-23 0:07 ` Tiemo Kieft
2004-01-23 15:57 ` foser
2004-01-23 17:18 ` dams
2004-01-23 19:14 ` [gentoo-desktop-research] Installer's Target user group Scott Koch
2004-01-24 0:47 ` foser
2004-01-23 20:18 ` Scott Koch
2004-01-24 14:55 ` foser
2004-01-25 0:07 ` Nathaniel McCallum
2004-01-24 19:19 ` Tom Hosiawa
2004-01-25 0:29 ` lukas
2004-01-25 1:00 ` Nathaniel McCallum
2004-01-25 1:12 ` lukas
2004-01-24 1:26 ` Steve Barnhart
2004-01-24 15:04 ` foser
2004-01-24 10:45 ` Paul de Vrieze
2004-01-24 14:50 ` foser
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=1074790970.1942.6.camel@localhost \
--to=spyderous@gentoo.org \
--cc=gentoo-desktop-research@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