On Tue, Jul 30, 2002 at 06:21:17AM +1000, Bruce Evans wrote:
> On Mon, 29 Jul 2002, Ruslan Ermilov wrote:
>
> > On Fri, Jul 19, 2002 at 10:55:56PM +1000, Bruce Evans wrote:
> > > On Fri, 19 Jul 2002, Ruslan Ermilov wrote:
> > > > OTOH, if we go this way we can get rid of ugly ${COPY} completely.
> > >
> > > I'd like to get rid of it too. But not in RELENG_4. -c has been the default
> > > for long enough now in -current. As you know, there are various problems
> > > in using the correctly named variable for install(1)'s flags (INSTALLFLAGS)
> > > to actually hold install's flags in a general way (mainly, this variable
> > > already exists and is used in a non-general way). However, the old hack
> > > of putting the flags in the same variable as the command still works well
> > > except for the -[Cp] vs -d conflict. This depends on the flags not being
> > > order-dependent.
> > >
> > OK, -[CpS] are now ignored with -d, and I've dropped support for COPY.
> > I have a question. Why COPY can't be removed from RELENG_4 as well?
> > Ports that use COPY (there are many of them) will see it as an empty
> > string.
>
> -c hasn't been the default for so long in RELENG_4, so I think the change
> has too lrge a risk/reward ratio.
>
Can you envision any breakage caused by me removing COPY?=-c from
RELENG_4's bsd.own.mk? We bootstrap install(1), so it's in my
opinion safe to assume that on a system without COPY in bsd.own.mk
install(1) copies files by default, no? bsd.port.mk and many
ports that use ${COPY} will substitute an empty string. If you
disagree, what do you propose? Remove any usages of COPY from
src/ and leave its definition in bsd.own.mk? What purpose would
it serve then?Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age
msg41525/pgp00000.pgp
Description: PGP signature
