From owner-cvs-ports Wed Mar 5 08:56:31 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA27425 for cvs-ports-outgoing; Wed, 5 Mar 1997 08:56:31 -0800 (PST) Received: from precipice.shockwave.com (ppp-206-170-5-44.rdcy01.pacbell.net [206.170.5.44]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA27419 for ; Wed, 5 Mar 1997 08:56:28 -0800 (PST) Received: from shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.8.4/8.7.3) with ESMTP id IAA20788; Wed, 5 Mar 1997 08:55:36 -0800 (PST) Message-Id: <199703051655.IAA20788@precipice.shockwave.com> To: Eivind Eklund cc: cvs-ports@freefall.freebsd.org, gpalmer@freebsd.org Subject: Re: cvs commit: ports/net/samba/pkg PLIST ports/net/samba Makefile ports/net/samba/files md5 ports/net/samba/patches patch-aa patch-ab In-reply-to: Your message of "Wed, 05 Mar 1997 13:56:57 +0100." <3.0.32.19970305135656.015e8e00@dimaga.com> Date: Wed, 05 Mar 1997 08:55:36 -0800 From: Paul Traina Sender: owner-cvs-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk From: Eivind Eklund Subject: Re: cvs commit: ports/net/samba/pkg PLIST ports/net/samba Makefile ports/net/samba/files md5 ports/net/samba/patches patch-aa patch-ab At 05:35 PM 3/4/97 -0800, Paul Traina wrote: >pst 97/03/04 17:35:21 > > Modified: net/samba Makefile > net/samba/files md5 > net/samba/patches patch-aa > net/samba/pkg PLIST > Removed: net/samba/patches patch-ab > Log: > upgrade to 1.9.16p11 > > Revision Changes Path > 1.12 +2 -2 ports/net/samba/Makefile > 1.8 +1 -1 ports/net/samba/files/md5 > 1.6 +65 -138 ports/net/samba/patches/patch-aa > 1.6 +3 -3 ports/net/samba/pkg/PLIST This port still has a 'version required' line of 1.9.15p8. Where? There still is a point in smbtar where you are asked to edit to show where smbclient is located (previous patch-ab); shouldn't we patch it? Suggested patch is at freefall:~eivind/samba/patch-ab No. It's reasonable to expect it in the path, so patch-ab is no longer necessary. Previously, it looked for it in ".". The idea is to minimize our patches. Also, your upgrade do not make the difference between superuser scripts and user scripts; the previous version of the port made this distinction. This will make anybody that upgrade have two different versions of the scripts (old in /usr/local/sbin, new in /usr/local/bin). A full replacement for patch-aa is at freefall:~eivind/samba/patch-aa I know, I wrote the last patch, but in 1.9.16, they actually have the concept of what is and isn't a superuser script, so now I am following their lead. Gary: I sent you an upgrade for samba from 1.9.15p8 to 1.9.16p11 a little more than a week ago, asking whether you wanted to commit it, you wanted me to commit it, or you wanted to commit another upgrade, or there was a reason for keeping samba at the present (15p8) version. I didn't even get a reply. I assume this is due to time-pressure (I'm a chronic procastinator myself); would it be an idea to put somebody else as maintainer? I can take it, if nescessary - I use samba and track new versions anyway. Eivind Eklund perhaps@yes.no http://maybe.yes.no/perhaps/ eivind@freebsd.org