Date: Fri, 7 Jun 2002 22:34:34 -0700 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: "J. Mallett" <jmallett@FreeBSD.ORG> Cc: "Steven G. Kargl" <kargl@troutmask.apl.washington.edu>, freebsd-current@FreeBSD.ORG Subject: Re: patches for [x]install Message-ID: <20020607223434.A69197@troutmask.apl.washington.edu> In-Reply-To: <20020607220824.A31273@FreeBSD.ORG>; from jmallett@FreeBSD.ORG on Fri, Jun 07, 2002 at 10:08:25PM -0700 References: <20020607215214.A28624@FreeBSD.ORG> <200206080503.g5853XnD069166@troutmask.apl.washington.edu> <20020607220824.A31273@FreeBSD.ORG>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jun 07, 2002 at 10:08:25PM -0700, J. Mallett wrote: > * From "Steven G. Kargl" <kargl@troutmask.apl.washington.edu> > > J. Mallett said: > > > * From "Steven G. Kargl" <kargl@troutmask.apl.washington.edu> > > > > J. Mallett said: > > > > > > > > No. The third patch is correct (see below); otherwise I could set > > > > INSTALL to " install -C" QED. > > > > > > And I could set BINOWN to something bogus. > > > > > > Don't protect the user by removing functionality. > > > > Well, if the first patch is acceptable, then we would > > be restoring documented functionality; otherwise, > > rev 1.55 of xinstall.c will remove functionality. > > Add the word "meaningful" before "functionality" in my statement, and realise > that overriding such things should ALWAYS be something you can do. Consider > cross-builds, and so on. > -- I don't really care which patches are applied. One patch fixes install(1) and the other set of patches augments the current breakage in install(1). Either set of patches is acceptable to me, while the current state of affairs is unacceptable in general. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020607223434.A69197>