`install-only' is what the regular XEmacs code uses, so let's use that. i
didn't know about this when i picked `just-install'.
btw i'm *sure* that at one point the standard was to have `make install' do
nothing but install.
----- Original Message -----
From: "Steve Youngs" <youngs(a)xemacs.org>
To: "XEmacs Beta" <xemacs-beta(a)xemacs.org>
Cc: "Ben Wing" <ben(a)666.com>
Sent: Friday, March 28, 2003 2:06 PM
Subject: Re: [AC] [PACKAGES] More package build fixing.
|--==> "BW" == Ben Wing <ben(a)666.com> writes:
BW> ok, in this case you have reverted a change i explicitly made.
BW> in such cases i think you should wait before auto-committing.
BW> i also thought that `make install' should not build by default,
BW> which is wrong.
That's correct, 'make install' not building by default is wrong. See
(Info-goto-node "(standards)Standard Targets"), in particular,
| Compile the program and copy the executables, libraries, and so on
| to the file names where they should reside for actual use. If
| there is a simple test to verify that a program is properly
| installed, this target should run that test.
"Compile the program and copy..." suggests to me that the 'install'
target should build anything first, if required.
BW> you should add a target like `install-only' if you make this
I have no objection to having a 'install-only' target, but
interestingly, that info node I mentioned above doesn't say anything
about 'install' targets that just install and don't build.
BTW, do you want "install-only" or "just-install"? Maybe I should
just pick one as the real target and make the other an alias to it?
|---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |