unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-devel@gnu.org
Subject: Re: setgroups
Date: 18 Apr 2003 01:10:56 +0200	[thread overview]
Message-ID: <87ptnk90u7.fsf@zagadka.ping.de> (raw)
In-Reply-To: <m3y928pwvw.fsf@multivac.cwru.edu>

prj@po.cwru.edu (Paul Jarc) writes:

> > 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?
> 
> Is the situation somehow different from that for getgroups?  I was
> just about to (try to) make a patch that would add setgroups similarly
> to how getgroups is done.

Yes, I think we should handle setgroups like the other optional
functions, even if there are better ways.  Consistency is more
important here.

-- 
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3  331E FAF8 226A D5D4 E405


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2003-04-17 23:10 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 ` setgroups Rob Browning
2003-04-17 22:43   ` setgroups Paul Jarc
2003-04-17 23:10     ` Marius Vollmer [this message]
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=87ptnk90u7.fsf@zagadka.ping.de \
    --to=mvo@zagadka.de \
    --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).