public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Harring <ferringb@gmail.com>
To: gentoo-portage-dev@lists.gentoo.org
Cc: "Gregory M. Turner" <gmt@malth.us>
Subject: Re: [gentoo-portage-dev] blech... (multijob/multiprocessing work-around for cygwin)
Date: Mon, 24 Sep 2012 17:35:05 -0700	[thread overview]
Message-ID: <20120925003505.GP5384@localhost> (raw)
In-Reply-To: <201209241305.35900.vapier@gentoo.org>

On Mon, Sep 24, 2012 at 01:05:35PM -0400, Mike Frysinger wrote:
> On Monday 24 September 2012 06:25:35 Gregory M. Turner wrote:
> > On cygwin, there is a problem with bi-directional pipe support in bash.
> > 
> > I used to solve this with an ugly reversion in portage and an
> > ultra-simple stubbification patch for multiprocessing.eclass (both
> > serialized everything).
> > 
> > However, this really sucked for numerous reasons, including the obvious
> > one: it makes stuff slow as hell.
> 
> if cygwin sucks, it doesn't get parallel jobs.  add stubs to the end of the 
> file to disable parallel support.
> 
> if is_cygwin ; then
> 	numjobs() { return 1; }
> 	multijob_init() { return 0; }
> 	...etc...
> fi
> 
> interleaving the cygwin logic otherwise makes it unmaintainable

Seconded; if cygwin environment sucks for this, just suppress the 
parallelization for it.  Better to be working then not, plus I doubt 
cygwin users are going to notice a huge diff in performance. :)

~harring


      reply	other threads:[~2012-09-25  3:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-24 10:25 [gentoo-portage-dev] blech... (multijob/multiprocessing work-around for cygwin) Gregory M. Turner
2012-09-24 16:08 ` Zac Medico
2012-09-24 19:17   ` Gregory M. Turner
2012-09-24 17:05 ` Mike Frysinger
2012-09-25  0:35   ` Brian Harring [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=20120925003505.GP5384@localhost \
    --to=ferringb@gmail.com \
    --cc=gentoo-portage-dev@lists.gentoo.org \
    --cc=gmt@malth.us \
    /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