On Wed, Oct 21, 2015 at 5:09 PM, Freddie Chopin <[email protected]>
wrote:

> I've just built and tested that on ArchLinux - with suid, without
> namespaces.
> The projects build fine and I can debug them without the "^c" flag, so I
> guess
> that for me it's a 100% success.
>

Thanks for testing it out!


>
> BTW - some time ago (after the discussion with Ben above) I've sent a
> request
> to reopen the feature request to enable namespaces in ArchLinux and this is
> the reply I got:
>
> > All your links say is that there are known problems in the stable kernel.
> > 4.3 is a ways off.
> >
> > Even then, the issue is that new problems keep coming up.
>
> The request was obviously denied, but who knows what the future will bring
> (;
>

I sure don't :). But in the meantime, suid should be roughly equivalent to
user namespaces as far as tup is concerned. The downside for suid of course
is that you need root access on the machine, which not everyone has in
certain circumstances.


>
> Maybe after a while (to discover potential problems) you could post a new
> release? The last one was published over a year ago, and there are already
> two
> major changes - Win64 support and namespaces. If you merge explicit
> variants
> too, there would be three (;
>
>
I'm going to try to incorporate Robert's win64 changes, which include
variant support for that platform. After that I'll make a new release.

I may still do the explicit-variant branch in the future just to simplify
the dependency checker, but I think it still needs some work for
simplifying the meaning of $(TUP_CWD) and $(TUP_SRCDIR) (TUP_SRCDIR is new
to that branch).

Thanks,
-Mike

-- 
-- 
tup-users mailing list
email: [email protected]
unsubscribe: [email protected]
options: http://groups.google.com/group/tup-users?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"tup-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to