public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Robbins <drobbins@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] new guides
Date: Wed Apr 11 00:29:01 2001	[thread overview]
Message-ID: <20010411002815.D15536@cvs.gentoo.org> (raw)
In-Reply-To: <3AD3F097.77E8750D@gentoo.org>; from AGottinger@t-online.de on Wed, Apr 11, 2001 at 07:50:15AM +0200

On Wed, Apr 11, 2001 at 07:50:15AM +0200, Achim Gottinger wrote:

> I think it is generally a good idea to add configure to the patch, because it
> is a bit confusing that the configure in work exists but does not work. So
> eigther it must be removed if configure.in gets modified or added to the
> patch.

I agree with your suggestion.  Sorry, I should have made that more clear in the
previous email.

> > Though I'll agree, it would be nice to have a Perl-free system (drobbins hides)
> 
> Unfortunately xfree requires perl, so it whould be a xfree free system
> too.

> BTW: It whould be nice to have a python free runtime system too (nothing
> personal this time, so no need to run or hide :-)).  This is impossible at
> the moment because of the env-update thing. It might be required on embedded
> platforms where disc space is rare (spython ~5MB).  I suggest recode
> env-update in bash or c.

Well, pkgmerge, ebuild and emerge are in python right now too.  I don't have a problem
if people want to start converting the more stable code to C++.  A good start would be
env-update and the .tbz2 functions (/usr/lib/python2.0/xpak.py).  Since we're moving to
an object framework, I think that C++ would be a better fit than C.

If anyone is interested in doing this, please contact me first.  Then I'll carefully
coordinate my work in python with yours.

Best Regards,

-- 
Daniel Robbins					<drobbins@gentoo.org>
President/CEO					http://www.gentoo.org 
Gentoo Technologies, Inc.			



  reply	other threads:[~2001-04-11  6:28 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-09 20:56 [gentoo-dev] new guides Daniel Robbins
2001-04-10 22:51 ` pbg1854
2001-04-10 23:11   ` Achim Gottinger
2001-04-11  0:13     ` Gontran
2001-04-11  0:47       ` Achim Gottinger
2001-04-11  1:02         ` Gontran
2001-04-11  1:55           ` Achim Gottinger
2001-04-11  3:08             ` Gontran
2001-04-11  3:16               ` Achim Gottinger
2001-04-10 23:26   ` Achim Gottinger
2001-04-10 23:51     ` Daniel Robbins
2001-04-11  0:19       ` Achim Gottinger
2001-04-11  0:29         ` Daniel Robbins [this message]
2001-04-11  0:51           ` Achim Gottinger
2001-04-12 16:14           ` Pete Gavin
2001-04-13  1:41             ` Pete Gavin
     [not found]               ` <20010413052441.A29405@kabbu.thehutt.org>
2001-04-13  4:07                 ` Achim Gottinger
2001-04-13  6:07                   ` Tom Flavel
2001-04-13  6:49                     ` Achim Gottinger
2001-04-13  9:21                     ` Daniel Robbins
2001-04-13 10:51                       ` Pete Gavin
2001-04-16 21:08                   ` Jerry A!
2001-04-17  6:28                     ` Achim Gottinger
  -- strict thread matches above, loose matches on Subject: below --
2001-04-12 17:42 datazone

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=20010411002815.D15536@cvs.gentoo.org \
    --to=drobbins@gentoo.org \
    --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