public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: hasufell@gentoo.org, Thomas Sachau <tommy@gentoo.org>,
	Samuli Suominen <ssuominen@gentoo.org>
Subject: Re: [gentoo-dev] New eclass: autotools-multilib-minimal
Date: Thu, 28 Feb 2013 09:30:14 +0100	[thread overview]
Message-ID: <20130228093014.62d3e9ce@pomiocik.lan> (raw)
In-Reply-To: <512EAD91.7030405@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1267 bytes --]

On Thu, 28 Feb 2013 02:06:25 +0100
hasufell <hasufell@gentoo.org> wrote:

> On 02/24/2013 11:39 PM, Samuli Suominen wrote:
> > On 24/02/13 02:34, hasufell wrote:
> >> Some people seem to feel uncomfortable with autotools-multilib, because
> >> it depends on autotools-utils.
> >>
> >> Instead of arguing whether it makes sense or not I'd propose a similar
> >> autotools related eclass.
> >>
> >> I also attach an example conversion of media-libs/libexif (the
> >> maintainer wants to keep the changes minimal).
> >> Effectively I am only (almost) changing the function names and not the
> >> ebuild code.
> > 
> > looks good, seems exactly what I wanted
> > 
> >> Feel free to propose a different eclass name.
> > 
> > whatever it will be, please make it shorter, like 'multiabi' maybe
> > 
> 
> I cleaned up some things.
> 
> 1) eclass renamed to multilib-minimal.eclass

You didn't like multilib-wrapper?

> 4) Introduced a DISABLE_MULTILIB variable for use of portage-multilib,
> which will disable all multilib related stuff. I am not sure if that's
> what they want, but I heard something like that.
> Tommy should comment on this.

Setting that variable would invalidate metadata cache.

-- 
Best regards,
Michał Górny

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 966 bytes --]

  reply	other threads:[~2013-02-28  8:30 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-24  0:34 [gentoo-dev] New eclass: autotools-multilib-minimal hasufell
2013-02-24  4:22 ` hasufell
2013-02-24 10:06   ` Michał Górny
2013-02-24 10:11     ` Diego Elio Pettenò
2013-02-24 14:17       ` hasufell
2013-02-24 14:33         ` Pacho Ramos
2013-02-27 13:01         ` Samuli Suominen
2013-02-27 20:13           ` Michał Górny
2013-02-27 20:15           ` Pacho Ramos
2013-02-24 14:57   ` Michał Górny
2013-02-24 15:12     ` hasufell
2013-02-24 15:12     ` Pacho Ramos
2013-02-24 15:53       ` Michał Górny
2013-02-24 16:21         ` Pacho Ramos
2013-02-24 16:28         ` Alexis Ballier
2013-02-24 16:58         ` Samuli Suominen
2013-02-24 18:56           ` Michał Górny
2013-02-24 19:40             ` hasufell
2013-02-24 18:05         ` [gentoo-dev] " Jonathan Callen
2013-02-24 18:18           ` Michał Górny
2013-02-24 16:22 ` [gentoo-dev] " Alexis Ballier
2013-02-24 16:42   ` hasufell
2013-02-24 18:46     ` Alexis Ballier
2013-02-24 22:39 ` Samuli Suominen
2013-02-28  1:06   ` hasufell
2013-02-28  8:30     ` Michał Górny [this message]
2013-02-28 15:16       ` hasufell
2013-03-02  2:50       ` hasufell
2013-03-02 15:07         ` Michał Górny
2013-03-02 15:13           ` hasufell

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=20130228093014.62d3e9ce@pomiocik.lan \
    --to=mgorny@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=hasufell@gentoo.org \
    --cc=ssuominen@gentoo.org \
    --cc=tommy@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