[Bug 241463] [NEW PORT] devel/scons-py3: scons for python3

2019-10-31 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241463 Ronald Klop changed: What|Removed |Added Attachment #208730|0 |1 is obsolete|

[Bug 241463] [NEW PORT] devel/scons-py3: scons for python3

2019-10-31 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241463 Ronald Klop changed: What|Removed |Added Attachment #208682|0 |1 is obsolete|

[Bug 241463] [NEW PORT] devel/scons-py3: scons for python3

2019-10-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241463 --- Comment #11 from Kubilay Kocak --- (In reply to Ronald Klop from comment #8) What are the conflicting files? If similar to other python packages/software, only a small proportion of expected files in non-python-version-specific locatio

[Bug 241463] [NEW PORT] devel/scons-py3: scons for python3

2019-10-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241463 --- Comment #10 from Kubilay Kocak --- (In reply to Ronald Klop from comment #7) Consumers requiring a specific version should be update to correctly declare their version support, at the same time that the scons port is updated to declare

[Bug 241463] [NEW PORT] devel/scons-py3: scons for python3

2019-10-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241463 --- Comment #9 from Kubilay Kocak --- (In reply to Sunpoet Po-Chuan Hsieh from comment #6) This is the better option. The scons port should do nothing but declare the versions *it* supports, and scons consumers ought to declare specificall

[Bug 241463] [NEW PORT] devel/scons-py3: scons for python3

2019-10-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241463 Ronald Klop changed: What|Removed |Added Attachment #208562|0 |1 is obsolete|

[Bug 241463] [NEW PORT] devel/scons-py3: scons for python3

2019-10-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241463 --- Comment #7 from Ronald Klop --- (In reply to Sunpoet Po-Chuan Hsieh from comment #6) Hi, would it be possible to make scons@py27 the default? So that existing ports need not be updated at once, but new ports can start using scons@py3x?

[Bug 241463] [NEW PORT] devel/scons-py3: scons for python3

2019-10-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241463 --- Comment #6 from Sunpoet Po-Chuan Hsieh --- Regarding using scons with python 3.x, my initial plan was to change its dependency from python 2.7 to python 3.x and patch dependent ports. But that's a long list and I failed to fix some port

[Bug 241463] [NEW PORT] devel/scons-py3: scons for python3

2019-10-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241463 --- Comment #5 from Sunpoet Po-Chuan Hsieh --- (In reply to Ronald Klop from comment #1) I think scons@py27 should be able to coexist with scons@py3x before python 2.7 EoL. In your proposal, it's scons and scons-py3. -- You are receiving

[Bug 241463] [NEW PORT] devel/scons-py3: scons for python3

2019-10-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241463 --- Comment #4 from Kubilay Kocak --- @Sunpoet Let me know if/how I can help figure out the best way forward, available on IRC (freenode) any time to assist. -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 241463] [NEW PORT] devel/scons-py3: scons for python3

2019-10-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241463 Kubilay Kocak changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu

[Bug 241463] [NEW PORT] devel/scons-py3: scons for python3

2019-10-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241463 Kubilay Kocak changed: What|Removed |Added Assignee|ports-b...@freebsd.org |sunp...@freebsd.org