From: Stefan Boresch <stefan@mdy.univie.ac.at>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] YP suite of programs out of date
Date: Thu, 14 Mar 2002 16:08:30 +0100 [thread overview]
Message-ID: <20020314150830.GE13662@mdy.univie.ac.at> (raw)
I am aware that there is a feature freeze for the 1.0 release.
However, I noticed that the NIS/YP suite of programs (yp-tools,
ypbind-mt and ypserv) is several versions out of date, and I am
wondering whether this should not be corrected before the 1.0 release.
I just submitted updated ebuilds for yp-tools and ypbind-mt to
bugs.gentoo.org since these were trivial to write. Still, I wouldn't
mind if someone with experience in ebuilds takes a look at "bugs" 1144
and 1146.
It am happy to build a ypserv package over the next days as well, which
in itself is also not difficult. However, I could neither get
the existing ypserv ebuild nor the latest ypserver package built from
source without some tweaking to do exactly what I want for my
machines here; thus any ypserv package/ebuild I could submit would
almost certainly not be usable out of the box. I guess one
probably should have the ebuild print a warning along the lines RTFM :-)
Comments welcome (any NIS/YP experts out there?)
Stefan
reply other threads:[~2002-03-14 15:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020314150830.GE13662@mdy.univie.ac.at \
--to=stefan@mdy.univie.ac.at \
--cc=gentoo-dev@gentoo.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