From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: ssuominen@gentoo.org
Subject: Re: [gentoo-dev] New eclass: autotools-multilib-minimal
Date: Wed, 27 Feb 2013 21:13:55 +0100 [thread overview]
Message-ID: <20130227211355.6bb356d2@pomiocik.lan> (raw)
In-Reply-To: <512E03BF.6020305@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1372 bytes --]
On Wed, 27 Feb 2013 15:01:51 +0200
Samuli Suominen <ssuominen@gentoo.org> wrote:
> On 24/02/13 16:17, hasufell wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > On 02/24/2013 11:11 AM, Diego Elio Pettenò wrote:
> >> On 24/02/2013 11:06, Michał Górny wrote:
> >>> Then don't put 'autotools' in the name.
> >>
> >> +1
> >>
> >
> > That would be multilib-minimal.eclass then?
>
> Sounds good to me.
>
> > ABCD also suggested something else:
> > autotools-multilib.eclass -> autotools-utils-multilib.eclass
>
> This makes sense too, autotools-multilib.eclass is misleading as it
> embeds the "unrelated" autotools-utils.eclass
>
> So it seems currently that some are against this eclass, some are
> against the whole idea and favour multilib-portage, some are against
> using autotools-utils.eclass for this, ...
> Some people are already committing the eclass version changes/fixes to
> tree, some are filing bug reports about bugs caused by it, ...
>
> It would be nice if people agreed but I guess that is not happening, so
> i'll be pushing this eclass to tree under name 'multilib-minimal.eclass'
> if I don't hear compelling arguments for not doing so, or in case you
> push it before me
No, don't do it. Or at least wait till I clean up multilib-build a bit.
--
Best regards,
Michał Górny
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 966 bytes --]
next prev parent reply other threads:[~2013-02-27 20:13 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 [this message]
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
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=20130227211355.6bb356d2@pomiocik.lan \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=ssuominen@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