Re: [PATCH] pkg_rolling-replace: use POSIX getopts(1) instead of getopt(1)

To: Michael Forney <mforney%mforney.org@localhost>
Subject: Re: [PATCH] pkg_rolling-replace: use POSIX getopts(1) instead of getopt(1)
From: Greg Troxel <gdt%lexort.com@localhost>
Date: Sat, 05 Jun 2021 20:45:55 -0400

Michael Forney <mforney%mforney.org@localhost> writes:

> pkg_rolling-replace is missing a dependency on misc/getopt. Thoughts
> on porting it to POSIX getopts(1) instead?

If you've actually tested it on NetBSD, and it works, and you can get it
committed in say 48h after we see if anybody else has reasons not to,
that seems fine to me.

(You didn't mention what system it fails on because of lack of getopt,
but it seems an uncommon one as this is the first report of this problem
in 15 years.  I'm fine with fixing it but I don't want to change things
to address corner cases in the few days before freeze.)

Attachment: signature.asc
Description: PGP signature

Follow-Ups:
- Re: [PATCH] pkg_rolling-replace: use POSIX getopts(1) instead of getopt(1)
  - From: Michael Forney

References:
- [PATCH] pkg_rolling-replace: use POSIX getopts(1) instead of getopt(1)
  - From: Michael Forney

Prev by Date: [PATCH] pkg_rolling-replace: use POSIX getopts(1) instead of getopt(1)
Next by Date: daily pkgsrc CVS update output
Previous by Thread: [PATCH] pkg_rolling-replace: use POSIX getopts(1) instead of getopt(1)
Next by Thread: Re: [PATCH] pkg_rolling-replace: use POSIX getopts(1) instead of getopt(1)
Indexes:

Home | Main Index | Thread Index | Old Index