From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: X-Spam-Status: No, score=-0.1 required=5.0 tests=DMARC_NONE,MAILING_LIST_MULTI autolearn=unavailable autolearn_force=no version=4.0.0 Received: from helix.mdy.univie.ac.at (helix.mdy.univie.ac.at [131.130.40.7]) by chiba.3jane.net (Postfix) with ESMTP id 49B332005FFB for ; Thu, 14 Mar 2002 09:11:58 -0600 (CST) Received: from loop.mdy.univie.ac.at (loop.mdy.univie.ac.at [131.130.40.12]) by helix.mdy.univie.ac.at (Postfix) with ESMTP id 60BEA223 for ; Thu, 14 Mar 2002 16:08:31 +0100 (CET) Received: by loop.mdy.univie.ac.at (Postfix, from userid 119) id 23D2F42F86; Thu, 14 Mar 2002 16:08:30 +0100 (CET) Date: Thu, 14 Mar 2002 16:08:30 +0100 From: Stefan Boresch To: gentoo-dev@gentoo.org Message-ID: <20020314150830.GE13662@mdy.univie.ac.at> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline User-Agent: Mutt/1.3.25i Subject: [gentoo-dev] YP suite of programs out of date Sender: gentoo-dev-admin@gentoo.org Errors-To: gentoo-dev-admin@gentoo.org X-BeenThere: gentoo-dev@gentoo.org X-Mailman-Version: 2.0.6 Precedence: bulk Reply-To: gentoo-dev@gentoo.org List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux developer list List-Unsubscribe: , List-Archive: X-Archives-Salt: 397732eb-e9d0-4656-a3e9-8b2c4cae3a53 X-Archives-Hash: dd86fc02a093ee6292b068ab9c68f442 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