From: Andrew Choi <akochoi@shaw.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Mac OS X Installer Package Script
Date: Fri, 05 Jul 2002 09:03:35 -0600 [thread overview]
Message-ID: <m2it3ub4jc.fsf@shaw.ca> (raw)
In-Reply-To: <200207050809.g6589JuM031350@stubby.bodenonline.com>
> [...]
>
> I don't think it should run configure/make install. That is best done the
> "normal" way. This script does not allow any arguments to configure or make,
> or indeed, choice of make program to run. Some of us have shell scripts
> to run configure in a special way, that can't be done either with
> this script.
Hi Jan,
It's useful to have a script like mac/make-package to generate a
Installer package for use as a `binary distribution'. The ability to
pass options to configure and make can be added. Most of the time,
I'll still be using `normal' way of configure and make.
> It seems a bit much to have to build an installer and then run that just
> to install Emacs. I would prefer to have an option to configure where
> to install the application (/Application by default is fine), and then
> "make install" installs everything. A script to build an installer is cool,
> but I would not like for it to be mandatory.
>
> Oh, another thing, "make install" should not install an emacs executable
> in $prefix/bin, since that executable can't be run without crashing.
I agree, these need to be fixed. I'll look at them when I can. Don't
worry. I don't intend to make the use of Installer mandatory.
> Just my thoughts,
>
> Jan D.
Andrew.
next prev parent reply other threads:[~2002-07-05 15:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-05 8:14 Mac OS X Installer Package Script Jan D.
2002-07-05 15:03 ` Andrew Choi [this message]
2002-07-07 7:24 ` Eric Gillespie
2002-07-08 6:04 ` Jan D.
[not found] <m21yajgtnp.fsf@shaw.ca>
2002-07-04 20:37 ` Andreas Schwab
-- strict thread matches above, loose matches on Subject: below --
2002-07-04 19:49 Andrew Choi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2it3ub4jc.fsf@shaw.ca \
--to=akochoi@shaw.ca \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).