Archives
Archives
| From: | Zac Medico <zmedico@g.o> |
|---|---|
| To: | gentoo-portage-dev@l.g.o |
| Subject: | Re: [gentoo-portage-dev] [PATCH v2] AbstractEbuildProcess: disable ipc_daemon under Windows Subsystem for Linux |
| Date: | Fri, 23 Sep 2016 03:48:35 |
| Message-Id: | CAMiTYSoTj7BBQA-PZT3DkcDJ8oOM6syrdRDCDqfq3H2BK02+fg@mail.gmail.com |
| 1 | On Thu, Sep 22, 2016 at 8:23 PM, Kerin Millar <kfm@×××××××××.net> wrote: |
| 2 | > Duly updated to use any instead of ==, as recommended by Brian Dolbec. |
| 3 | > |
| 4 | > -- |
| 5 | > Kerin Millar <kfm@×××××××××.net> |
| 6 | |
| 7 | My first choice would be to use a small test case to detect when ipc |
| 8 | is broken, and disable it dynamically. A good example of such a test |
| 9 | is the can_poll_device function here: |
| 10 | |
| 11 | https://gitweb.gentoo.org/proj/portage.git/tree/pym/portage/util/_eventloop/EventLoop.py?h=portage-2.3.1#n597 |
| 12 | |
| 13 | If it's not possible to use a test similar to the above, maybe it's |
| 14 | best to use /proc/version or /proc/sys/kernel/osrelease as mentioned |
| 15 | in the following issue: |
| 16 | |
| 17 | https://github.com/Microsoft/BashOnWindows/issues/423 |
| 18 | |
| 19 | Thanks, |
| 20 | Zac |
| Subject | Author |
|---|---|
| Re: [gentoo-portage-dev] [PATCH v2] AbstractEbuildProcess: disable ipc_daemon under Windows Subsystem for Linux | Kerin Millar <kfm@×××××××××.net> |