From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: setgroups
Date: Thu, 17 Apr 2003 17:29:25 -0500 [thread overview]
Message-ID: <87brz4dagq.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <m3y928ripu.fsf@multivac.cwru.edu> (prj@po.cwru.edu's message of "Thu, 17 Apr 2003 16:07:03 -0400")
(Followups set to guile-devel -- I think...)
prj@po.cwru.edu (Paul Jarc) writes:
> Not a bug, really, but a significant (to me, anyway :) ) missing
> feature. Can we have setgroups?
I saw this and was about to just add it, but then realized I didn't
know what our policies were wrt to functions that might or might not
exist at runtime...
If I'm not mistaken, setgroups might or might not be available on a
given system. We can test for it in configure and optionally define
it in posix.c (or maybe elsewhere since it's not posix...), but then
what?
Given our current uncertainty about compilation, it seems like
(if (defined? 'setgroups) ...)
might be a bad idea for the long term, so how would we want to handle
this, via (provided? 'setgroups)? i.e. is provided? supposed to be
used for things at that fine a granularity? Also, it'd be nice if we
could use something that could in theory be optimized away like this
(though we probably wouldn't want this exactly...):
(define-constant *have-setgroups?* ...)
...
(if *have-setgroups?* ...)
etc.
Thanks
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next parent reply other threads:[~2003-04-17 22:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3y928ripu.fsf@multivac.cwru.edu>
2003-04-17 22:29 ` Rob Browning [this message]
2003-04-17 22:43 ` setgroups Paul Jarc
2003-04-17 23:10 ` setgroups Marius Vollmer
2003-04-18 3:19 ` setgroups Rob Browning
2003-04-17 23:20 ` setgroups Paul Jarc
2003-04-18 3:34 ` setgroups Rob Browning
2003-04-18 10:31 ` setgroups Marius Vollmer
2003-04-18 15:37 ` setgroups Paul Jarc
2003-04-18 17:38 ` setgroups Paul Jarc
2003-04-18 17:49 ` setgroups Paul Jarc
2003-04-21 16:20 ` setgroups Paul Jarc
2003-04-18 15:41 ` setgroups Rob Browning
2003-04-18 16:00 ` setgroups Paul Jarc
2003-04-18 17:01 ` setgroups Rob Browning
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87brz4dagq.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).