From: AGottinger@t-online.de (Achim Gottinger)
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] new guides
Date: Wed Apr 11 00:19:01 2001 [thread overview]
Message-ID: <3AD3F097.77E8750D@gentoo.org> (raw)
In-Reply-To: 20010410235052.B15536@cvs.gentoo.org
Daniel Robbins wrote:
>
> On Wed, Apr 11, 2001 at 06:56:57AM +0200, Achim Gottinger wrote:
>
> > In situations where we modify aclocal or configure.in, i think it is better
> > to run autoconf/... and add a patch for all modified files instead of running
> > autoconf from the ebuild. This simplifies package dependencies and makes it
> > possible to build all packages without autoconf/automake/m4/perl installed.
>
> I don't think that this really matters for packages like GNOME (after all, if
> you're installing GNOME then you probably also have autoconf/Perl,etc.
> installed :), but this technique would be useful for critical system packages,
> like those found in sys-*.
I had the following problem with glibc-2.2.2. Their configure file was
not designed well and some
tests failed on a system without perl (build). I liked petes suggestion
to modify the root and not the leaf
of the configuration, so I patched configure.in.
So now I had to compile autoconf/m4/perl/libtool before I could build
glibc (very bad).
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.
However, "emerge" should be able to sort out the
> build/runtime deps perfectly in either case -- as long as the DEPEND and
> RDEPEND strings are set correctly.
Yes that's true. But in the above example it is a problem.
>
> 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.
achim~
>
> --
> Daniel Robbins <drobbins@gentoo.org>
> President/CEO http://www.gentoo.org
> Gentoo Technologies, Inc.
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://www.gentoo.org/mailman/listinfo/gentoo-dev
next prev parent reply other threads:[~2001-04-11 6:18 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 [this message]
2001-04-11 0:29 ` Daniel Robbins
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=3AD3F097.77E8750D@gentoo.org \
--to=agottinger@t-online.de \
--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