From: westin*nospam@graphics.cornell.edu (Stephen H. Westin)
Subject: Re: emacs for Mac OS 10.3.1
Date: 21 Nov 2003 13:58:50 -0500 [thread overview]
Message-ID: <uoev55z11.fsf@graphics.cornell.edu> (raw)
In-Reply-To: slrnbrsmc8.7bk.hwolf@esb.dsl.bbn.com
Hugh Wolf <hwolf@deutsches.lieder.de> writes:
> On 2003-11-21, Stephen H. Westin <westin*nospam@graphics.cornell.edu> wrote:
> > I still haven't figured out the point to Fink.
>
> The main reason is version control and dependency management. It's
> just like using dselect etc in Debian or rpm in Redhat. It makes no
> sense at all to build straight from tars imo if you have a good
> software package manager available.
>
> An important secondary reason in because lots of unix packages need
> minor adjustments to build and/or run in osx, and the kind volunteers
> at fink have already created the .patch files for the rest of us to
> use.
>
> Thirdly, in many cases prebuilt fink binary packages are available
> for download. Why build it yourself if it's already been done for
> you in a sensible way?
>
>
> All in all, why would you _not_ want to use fink?
Because it puts everything in a strange place where it isn't found by
most normal open-source software builds.
> What advantages
> are you gaining by building everything manually yourself? I can't
> think of any.
Well, I was exposed to Fink in trying to port code from Linux. When I
went to build, say, libgphoto2, everything was broken, using the wrong
version of utilities, etc.
There are plenty of open-source projects, including Emacs, that have
integrated the Mac port into the main source tree and build procedure.
--
-Stephen H. Westin
Any information or opinions in this message are mine: they do not
represent the position of Cornell University or any of its sponsors.
next prev parent reply other threads:[~2003-11-21 18:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 20:18 emacs for Mac OS 10.3.1 Chris Swoyer
2003-11-19 21:03 ` Hugh Wolf
2003-11-19 21:48 ` Tim McNamara
2003-11-20 12:51 ` Hugh Wolf
2003-11-21 17:52 ` Stephen H. Westin
2003-11-21 18:29 ` Hugh Wolf
2003-11-21 18:58 ` Stephen H. Westin [this message]
2003-11-21 19:25 ` Kevin Rodgers
2003-11-21 19:34 ` Tim McNamara
2003-11-21 18:33 ` Tim McNamara
2003-11-21 21:02 ` Hugh Wolf
2003-11-20 2:40 ` leo
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=uoev55z11.fsf@graphics.cornell.edu \
--to=westin*nospam@graphics.cornell.edu \
/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.
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).