bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: noloader@gmail.com
Cc: bug-gnulib@gnu.org
Subject: Re: Apple embedded OSes
Date: Sun, 27 Dec 2020 13:19:58 +0100	[thread overview]
Message-ID: <2095420.aIqRkdFbnS@omega> (raw)
In-Reply-To: <CAH8yC8=z5eiPQwrYgNp8rx7aX64AEjFn8WfoSPtwnU=YLzz1aQ@mail.gmail.com>

Hi Jeffrey,

> Just an FYI in case you have not hit this wall (yet?)... The exec
> family, posix_spawn and friends are _not_ available on all Apple
> platforms. Be sure to check availability before using them.
> 
> For example, the iPhone/iPad SDKs has them, but the WatchOS and TvOS
> SDKs lack them. To further complicate matters, you have to include
> <TargetConditionals.h> before you can check for the SDK.

There are 3 questions:

1) Do you think it is technically possible to support the iOS variants
   in Gnulib?

2) Do you think it makes sense for the GNU project to support the iOS
   variants?

3) Do you think we need to document that Gnulib doesn't support the iOS
   variants?

My take on these questions would be:

1) For an OS that does not have files with file names, it's pointless to
   even think about open(), exec(), and so on.

2) Anyone buying and using these devices has surrendered their entire
   freedom and privacy to Apple. There is no point for GNU to help make
   these devices more widely spread by porting software to it.

3) I would think that the communities of POSIX / C users and iOS / Swift
   users are disjoint. Hence no need to document.

Your take?

Bruno



  reply	other threads:[~2020-12-27 12:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-26 13:53 new modules execve, execvpe, execvp, execv, execl, execle, execlp Bruno Haible
2020-12-27 11:15 ` Jeffrey Walton
2020-12-27 12:19   ` Bruno Haible [this message]
2020-12-27 19:08     ` Apple embedded OSes Jeffrey Walton

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://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2095420.aIqRkdFbnS@omega \
    --to=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=noloader@gmail.com \
    /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).