[Bug 238669] textproc/py-recommonmark: Missing USE_PYTHON=concurrent

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238669 Kubilay Kocak changed: What|Removed |Added Assignee|bro...@freebsd.org |y...@freebsd.org --- Comment #3 fr

[Bug 238669] textproc/py-recommonmark: Missing USE_PYTHON=concurrent

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238669 Fukang Chen changed: What|Removed |Added Status|Open|Closed Resolution|---

[Bug 238669] textproc/py-recommonmark: Missing USE_PYTHON=concurrent

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238669 Kubilay Kocak changed: What|Removed |Added CC||pyt...@freebsd.org Sever

[Bug 220214] Try to handle man files for USE_PYTHON=concurrent

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220214 --- Comment #9 from commit-h...@freebsd.org --- A commit references this bug: Author: mat Date: Tue Dec 19 16:23:49 UTC 2017 New revision: 456737 URL: https://svnweb.freebsd.org/changeset/ports/456737 Log: Enhance USES=uniquefiles to be

[Bug 220214] Try to handle man files for USE_PYTHON=concurrent

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220214 Mathieu Arnold changed: What|Removed |Added Status|Open|Closed Resolution|---

[Bug 220214] Try to handle man files for USE_PYTHON=concurrent

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220214 Antoine Brodin changed: What|Removed |Added Flags|exp-run?|exp-run+ --- Comment #8 from Anto

[Bug 220214] Try to handle man files for USE_PYTHON=concurrent

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220214 --- Comment #7 from Fukang Chen --- Thanks mat@ and antoine@ :) -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-python@freebsd.org mailing list https://li

[Bug 220214] Try to handle man files for USE_PYTHON=concurrent

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220214 --- Comment #6 from Mathieu Arnold --- Created attachment 188835 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=188835&action=edit v2 fix those two ports. -- You are receiving this mail because: You are on the CC list for the

[Bug 220214] Try to handle man files for USE_PYTHON=concurrent

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220214 --- Comment #5 from Mathieu Arnold --- Sure, testing. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-python@freebsd.org mailing list https://lists.freebs

[Bug 220214] Try to handle man files for USE_PYTHON=concurrent

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220214 --- Comment #4 from Antoine Brodin --- I expect problems with at least 2 ports: - mail/py-pymailq - math/py-numpy Can you provide patch for them? -- You are receiving this mail because: You are on the CC list for the bug. __

[Bug 220214] Try to handle man files for USE_PYTHON=concurrent

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220214 Mathieu Arnold changed: What|Removed |Added Flags||exp-run? -- You are receiving th

[Bug 220214] Try to handle man files for USE_PYTHON=concurrent

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220214 Mathieu Arnold changed: What|Removed |Added Attachment #183717|0 |1 is obsolete|

[Bug 220214] Try to handle man files for USE_PYTHON=concurrent

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220214 --- Comment #2 from Fukang Chen --- Created attachment 184080 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=184080&action=edit minor update example: UNIQUE_SUFFIX_TYPES+= SUFFIX_MAN UNIQUE_SUFFIX_MAN_FILES= man/man1/com

[Bug 220214] Try to handle man files for USE_PYTHON=concurrent

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220214 --- Comment #1 from Mathieu Arnold --- I think locking it to man pages is a bad idea. It should be more generic, something along the lines of a *_WITH_SUFFIX variable or *_WITH_EXT or something. -- You are receiving this mail because: You

[Bug 220214] Try to handle man files for USE_PYTHON=concurrent

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220214 Kubilay Kocak changed: What|Removed |Added CC||ko...@freebsd.org,

Re: USE_PYTHON=concurrent

I am not sure >> > how concurrent is supposed to work: >> > >> > I looked in /usr/ports/Mk and only found a documentation reference to >> > 'concurrent'. Setting USE_PYTHON=concurrent doesn't appear to actually >> > change any beh

Re: USE_PYTHON=concurrent

> I looked in /usr/ports/Mk and only found a documentation reference to > > 'concurrent'. Setting USE_PYTHON=concurrent doesn't appear to actually > > change any behaviour. > > > > Please could you explain this for me? > > From “/usr/ports/Mk/

Re: USE_PYTHON=concurrent

On Mon, Mar 30, 2015 at 09:14:40PM +0200, David Naylor wrote: > Hi, > > I am investigating converting my ports to concurrent however I am not sure > how concurrent is supposed to work: > > I looked in /usr/ports/Mk and only found a documentation reference to > 'concur

USE_PYTHON=concurrent

Hi, I am investigating converting my ports to concurrent however I am not sure how concurrent is supposed to work: I looked in /usr/ports/Mk and only found a documentation reference to 'concurrent'. Setting USE_PYTHON=concurrent doesn't appear to actually change any behav