On Tue, May 01 2018, IL Ka wrote:
>>
>> Take it from someone who has been working with ports on OpenBSD for 12+
>> years, FLAVORs are not the answer.
>>
> Hm... What is wrong with flavors?
>
>> just mount /home with wxallowed, or use a different filesystem
> I rebuilt python without of wxneeded f
On Tue, May 01, 2018 at 04:39:07PM +0300, IL Ka wrote:
> >
> > Take it from someone who has been working with ports on OpenBSD for 12+
> > years, FLAVORs are not the answer.
> >
> Hm... What is wrong with flavors?
>
> > just mount /home with wxallowed, or use a different filesystem
> I rebuilt py
>
> Take it from someone who has been working with ports on OpenBSD for 12+
> years, FLAVORs are not the answer.
>
Hm... What is wrong with flavors?
> just mount /home with wxallowed, or use a different filesystem
I rebuilt python without of wxneeded from ports, and it works now.
Do you think thi
Take it from someone who has been working with ports on OpenBSD for 12+
years, FLAVORs are not the answer.
Unless you have an idea about how to get rid of W+X mappings in WebKit
and py-cryptography, just mount /home with wxallowed, or use a different
filesystem for home directories for users that
Then I beg you for patches. Good luck!
I was trying to say that port maintainer added wxneded to python and fixed
issues with packages
that use WX (i.e. py- cryptography). I assume they did not work without of
it.
And now they work for python running in /usr/local (because it is
wxallowed by default).
I am not native English speaker, s
On Tue, 1 May 2018 03:13:23 +0300, IL Ka
wrote:
> To fix it, I rebuild python from ports using USE_WXNEEDED=no
> It solved my problem, but I do not want to build Python from ports,
> so better solution would be to
> * Accept your patch and create 2 flavors of python
> * Or set USE_WXNEEDED=no by
On Tue, May 01, 2018 at 03:13:23AM +0300, IL Ka wrote:
> Hi,
>
> > Can you please give me a link to fix?
> Sorry, I misunderstood you.
>
You said "thank you for fixing py-cryptography".
I didn't notice that fix.
> I run snapshot and it has wxallowed for /usr/local by default (I haven't
> touched
Hi,
> Can you please give me a link to fix?
Sorry, I misunderstood you.
I run snapshot and it has wxallowed for /usr/local by default (I haven't
touched it).
$ grep wxallowed /etc/fstab
4154a363527e316f.h /usr/local ffs rw,wxallowed,nodev 1 2
python is wxneeded since 2016 in OpenBSD:
https://git
On Mon, Apr 30, 2018 at 03:22:21PM -0700, Il Ka wrote:
> Thank you for fixing py-cryptography in /usr/local,
> but we now have python that can't be launched from home
> (because it is not wxallowed).
>
Hi!
Can you please give me a link to fix?
(I hope you didn't say sarcasm)
> And it breaks vi
Thank you for fixing py-cryptography in /usr/local,
but we now have python that can't be launched from home
(because it is not wxallowed).
And it breaks virtualenv:
https://marc.info/?l=openbsd-misc&m=152510694522191&w=2
virtualenv is used by almost any python developer, and we rendered
it to u
On Fri, Jan 26, 2018 at 05:36:00PM +0200, mazocomp wrote:
> Landry, if I install unpatched port, it refuses to run with "permission
> denied" error. In this case I have to forget about binary updating and
> compile this port manually.
Then you get a real reason to help fixing the actual issue, ins
Landry, if I install unpatched port, it refuses to run with "permission
denied" error. In this case I have to forget about binary updating and
compile this port manually.
On 2018/01/26 17:17, mazocomp wrote:
> On Fri, Jan 26, 2018 at 02:56:11PM +, Stuart Henderson wrote:
> > On 2018/01/26 16:36, mazocomp wrote:
> > > +Flavor wx - build with W|X reliance.
> >
> > Of course we have thought about this before! But it's not as simple as
> > you propose. Done in
On Fri, Jan 26, 2018 at 02:56:11PM +, Stuart Henderson wrote:
> On 2018/01/26 16:36, mazocomp wrote:
> > +Flavor wx - build with W|X reliance.
>
> Of course we have thought about this before! But it's not as simple as
> you propose. Done in the way you suggest as a simple either/or flavou
On Fri, Jan 26, 2018 at 04:59:40PM +0200, mazocomp wrote:
> On Fri, Jan 26, 2018 at 03:49:48PM +0100, Solène Rapenne wrote:
> > Le 2018-01-26 15:36, mazocomp a écrit :
> > > # Python itself is clean, but some extensions e.g. py-cryptography
> > > # and QtWebKit require W|X mappings.
> > > +.if ${
On Fri, Jan 26, 2018 at 03:49:48PM +0100, Solène Rapenne wrote:
> Le 2018-01-26 15:36, mazocomp a écrit :
> > # Python itself is clean, but some extensions e.g. py-cryptography
> > # and QtWebKit require W|X mappings.
> > +.if ${FLAVOR} == "wx"
> > USE_WXNEEDED = Yes
> > +.endif
> >
> > .if ${
On 2018/01/26 16:36, mazocomp wrote:
> +Flavor wx - build with W|X reliance.
Of course we have thought about this before! But it's not as simple as
you propose. Done in the way you suggest as a simple either/or flavour
is going to cause too many problems and confusion with dependent ports
and
If you don't like wxallowed/wxneeded, great, that's the point!
But the way forward is to fix offenders, not to pretend you can sweep
the problem under the rug with untested diffs.
--
jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
Le 2018-01-26 15:36, mazocomp a écrit :
# Python itself is clean, but some extensions e.g. py-cryptography
# and QtWebKit require W|X mappings.
+.if ${FLAVOR} == "wx"
USE_WXNEEDED = Yes
+.endif
.if ${VERSION} == "3.6"
ALL_TARGET = all
IIRC python doesn't have W^X issue but some python l
diff --git lang/python/2.7/pkg/DESCR-main lang/python/2.7/pkg/DESCR-main
index adfd63f9840..9d7c54a9e93 100644
--- lang/python/2.7/pkg/DESCR-main
+++ lang/python/2.7/pkg/DESCR-main
@@ -12,3 +12,5 @@ written in C or C++. On most systems such modules may be
dynamically loaded. Python is also adapta
21 matches
Mail list logo
