public inbox for gentoo-python@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: Marien Zwart <marienz@gentoo.org>
Cc: gentoo-python <gentoo-python@lists.gentoo.org>,
	Gentoo Python Project <python@gentoo.org>
Subject: Re: [gentoo-python] Re: python-any-r1 and MERGE_TYPE
Date: Sat, 12 Oct 2013 13:16:31 +0200	[thread overview]
Message-ID: <20131012131631.23771307@gentoo.org> (raw)
In-Reply-To: <CAEWfL_RDjnB+_JoaAJcPt0pRPLe8=sqcYBhZmkF4=T7P0qDRDw@mail.gmail.com>

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

Dnia 2013-10-11, o godz. 20:04:57
Marien Zwart <marienz@gentoo.org> napisał(a):

> On Fri, Oct 11, 2013 at 10:05 AM, Mike Gilbert <floppym@gentoo.org> wrote:
> > On Thu, Oct 10, 2013 at 4:04 PM, Michał Górny <mgorny@gentoo.org> wrote:
> >> Therefore, I think it would be beneficial to add the MERGE_TYPE check
> >> inside pkg_setup. In case someone needs Python during binary package
> >> install, we can (likely in the future):
> >>
> >> 1. add a variable to disable the MERGE_TYPE check,
> >>
> >> 2. add a new function that does the actual Python setup and make
> >> the default pkg_setup() a common-case wrapper for it.
> >>
> >> What are your thoughts?
> >
> > #2 sounds like a solid plan.
> 
> Sounds good to me.

I have added the MERGE_TYPE check then. I think we can
add the dedicated function when someone actually needs it.

-- 
Best regards,
Michał Górny

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

      reply	other threads:[~2013-10-12 11:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-10 20:04 [gentoo-python] python-any-r1 and MERGE_TYPE Michał Górny
2013-10-10 23:05 ` [gentoo-python] " Mike Gilbert
2013-10-11  9:04   ` Marien Zwart
2013-10-12 11:16     ` Michał Górny [this message]

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=20131012131631.23771307@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-python@lists.gentoo.org \
    --cc=marienz@gentoo.org \
    --cc=python@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