public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Haubenwallner <haubi@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] New eclass for x11 packages
Date: Mon, 22 Feb 2010 11:50:26 +0100	[thread overview]
Message-ID: <4B826172.4010102@gentoo.org> (raw)
In-Reply-To: <4B7DC046.7010001@gentoo.org>



Tomáš Chvátal wrote:
> Hi,
> we prepared new eclass for x11 packages that should be used as
> replacement for x-modular.eclass.

> Prefix support done.

There's one thing I don't find addressed yet:

When some patch[1] necessary for some (prefix-) platform has to touch
configure.ac or Makefile.am, rendering eautoreconf mandatory on
*each* platform, there's no way to tell xorg-2_reconf_source() to
do the eautoreconf instead of elibtoolize *unconditionally*.

We had to have libXaw.ebuild do the eautoreconf unconditionally[2] after
x-modular_src_unpack() - which just did elibtoolize on some platforms,
causing elibtoolize to get run twice, resulting in bug#232820 [3].

Even if libXaw doesn't need those patches any more it seems,
there's no reason such patches won't become necessary again.

[1] http://overlays.gentoo.org/proj/alt/browser/trunk/prefix-overlay/x11-libs/libXaw/files/libXaw-1.0.5-darwin.patch?rev=37037
[2] http://overlays.gentoo.org/proj/alt/browser/trunk/prefix-overlay/x11-libs/libXaw/libXaw-1.0.6.ebuild?rev=49677#L43
[3] http://bugs.gentoo.org/show_bug.cgi?id=232820

/haubi/

PS: Just a suggestion what an ebuild could do in this case:
 src_prepare() {
     xorg-2_src_prepare --force-eautoreconf
 }
-- 
Michael Haubenwallner
Gentoo on a different level



  parent reply	other threads:[~2010-02-22 11:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-18 22:33 [gentoo-dev] [RFC] New eclass for x11 packages Tomáš Chvátal
2010-02-18 22:39 ` Jeremy Olexa
2010-02-18 23:04   ` Tomáš Chvátal
2010-02-18 23:06 ` Tomáš Chvátal
2010-02-18 23:11 ` David Leverton
2010-02-18 23:16   ` Tomáš Chvátal
2010-02-18 23:20     ` Tomáš Chvátal
2010-02-18 23:22     ` David Leverton
2010-02-19  1:22 ` [gentoo-dev] " Ryan Hill
2010-02-24 20:54   ` Tomáš Chvátal
2010-02-22 10:50 ` Michael Haubenwallner [this message]
2010-02-22 14:20   ` [gentoo-dev] " Tomáš Chvátal
2010-02-22 15:50     ` Michael Haubenwallner
2010-02-22 15:57       ` Tomáš Chvátal
2010-02-27 12:18         ` Tomáš Chvátal
2010-03-01  8:58           ` Michael Haubenwallner
2010-03-01 10:38             ` Samuli Suominen
2010-03-07 10:52               ` Rémi Cardona
2010-03-10 14:13 ` Tomáš Chvátal
2010-03-10 19:40   ` Dawid Węgliński
2010-03-10 19:42     ` Tomáš Chvátal

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=4B826172.4010102@gentoo.org \
    --to=haubi@gentoo.org \
    --cc=gentoo-dev@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